Handover processing method and base station

ABSTRACT

A handover processing method and a base station are provided. The method includes: receiving a handover request message sent by a source base station or a core network node; sending a first message, according to the handover request message, to a second target base station to notify the second target base station that a handover of part or all of a service of a user equipment to the second target base station is to be performed; and sending a handover request acknowledge message to the source base station or the core network node to notify the source base station or the core network node to hand over the user equipment to at least one target cell of the first target base station and/or at least one target cell of the second target base station. The present application realizes a multi-cell handover.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/435,020, filed on Feb. 16, 2017, which is a continuation of U.S.patent application Ser. No. 14/615,145, filed on Feb. 5, 2015, now U.S.Pat. No. 9,596,624, which is a continuation of International ApplicationNo. PCT/CN2012/079779, filed on Aug. 7, 2012. All of the afore-mentionedpatent applications are hereby incorporated by reference in theirentireties.

TECHNICAL FIELD

Embodiments of the present invention relate to a field of communication,and particularly relates to a handover processing method and a basestation.

BACKGROUND

In conventional art, when a base station, which serves a user equipment(UE), is not suitable for servicing it, the UE will be handed over toanother base station. In the prior art, the process is achieved by afollowing manner.

A source base station (for example, an evolved NodeB (eNB)) sends ahandover request message to a target eNB.

If the handover is accepted, the target eNB points out, in a handoverrequest acknowledge (Handover Request ACK) message, a tunnel endpointGeneral Packet Radio Service (GPRS) tunneling protocol (GPRS TunnelingProtocol, GTP for short) where forwarding data is expected to bereceived. The GTP tunnel endpoint includes a transport layer address anda GTP Tunnel Endpoint Identifier (Tunnel Endpoint ID, or TEID).

After receiving the Handover Request ACK message, a source eNB indicatesthat the UE hands over from the source eNB to the target eNB.

The inventor found that, in the conventional art, a handover flow canmerely hand over a UE from one cell to another cell, and a handovercould not performed when there exists more than one source cell ortarget cell.

SUMMARY

In view of this, the application provides a handover processing solutionto solve a problem in the conventional art that a handover could not beperformed when there exists more than one source cell or target cell.

In one aspect, a handover processing method is provided, including:receiving, by a first target base station, a handover request messagesent by a source base station or a core network node; sending, by thefirst target base station, a first message, according to the handoverrequest message, to a second target base station to notify the secondtarget base station that a handover of part or all of a service of auser equipment to the second target base station is to be performed; andsending, by the first target base station, a handover requestacknowledge message to the source base station or the core network node,wherein the handover request acknowledge message is used for notifyingthe source base station or the core network node to hand over the userequipment to at least one target cell of the first target base stationand/or at least one target cell of the second target base station.

In a first possible implementation manner of a first aspect, thesending, by the first target base station, a first message, according tothe handover request message, to the second target base station,includes:

determining, by the first target base station, that the handover of thepart or all of the service of the user equipment to a target cell of thesecond target base station is to be performed according to a measurementreport of the user equipment and/or radio access bear RAB information ofthe user equipment in the handover request message; or determining, bythe first target base station, that the handover of part or all of theservice of the user equipment to the second target base station is to beperformed according to information of a target cell of the second targetbase station in the handover request message; and

sending, by the first target base station, the first message to thesecond target base station.

In combination with the first aspect or the first possibleimplementation manner of the first aspect, in a second possibleimplementation manner, the handover request message includes at leastone of followings: information of at least one target cell of the secondtarget base station, measurement report information of the userequipment, context information of the user equipment and information ofa service of the user equipment, wherein the information of the serviceincludes RAB information of the service.

In combination with the first aspect, the first possible implementationmanner of the first aspect, or the second possible implementation mannerof the first aspect, in a third possible implementation manner, thefirst message includes: information of at least one service of the userequipment, wherein the information of the service includes RABinformation of the service and/or configuration information of a radiobear RB.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, or the third possible implementation manner of thefirst aspect, in a fourth possible implementation manner, theinformation of the service further includes at least one of followings:configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information, wherein theconfiguration coordination information of the radio resource of the RBincludes at least one of followings: a physical cell identifier, a logiccell identifier, a virtual cell identifier, frequency information,carrier information, radio resource block information, subcarrierinformation, sub-frame information, time domain information, code domaininformation and space domain information; the split indicationinformation includes data split information based on an RB or data splitinformation based on a packet.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, or the fourth possible implementation manner of the firstaspect, in a fifth possible implementation manner, the GTP tunnelendpoint information is first type of GTP tunnel endpoint information orfourth type of GTP tunnel endpoint information, wherein the first typeof GTP tunnel endpoint information is used for establishing atransmission bearer of an S1 interface between a serving gateway S-GWand the first target base station and/or the second target base station,and the fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,or the fifth possible implementation manner of the first aspect, in asixth possible implementation manner, the configuration information ofthe RB includes: configuration information of a packet data convergenceprotocol PDCP layer, a radio link control RLC layer, a medium accesscontrol MAC layer and a physical layer; or configuration information ofan RLC layer, an MAC layer and a physical layer.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, or thesixth possible implementation manner of the first aspect, in a seventhpossible implementation manner, after the sending, by the first targetbase station, the first message to the second target base station, themethod further includes: receiving, by the first target base station, asecond message sent by the second target base station, wherein thesecond message is used for indicating information regarding whether thehandover of the part or all of the service of the user equipment to thesecond target base station is accepted by the second target basestation.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, or the seventhpossible implementation manner of the first aspect, in an eighthpossible implementation manner, the second message includes at least oneof followings: an identifier of the user equipment, first informationand indication information, wherein the indication information includesat least one of followings: indication information of refusing thehandover of the part or all of the service of the user equipment to thesecond target base station, indication information of accepting thehandover of the part or all of the service of the user equipment to thesecond target base station, and indication information of modifying thefirst message; the first information includes at least one offollowings: an identifier of an RB accepted by the second target basestation, configuration information of an RB accepted by the secondtarget base station, an identifier of an RAB corresponding to an RBaccepted by the second target base station, an identifier of an RB whoseresource configuration is rejected by the second target base station,and an identifier of an RAB corresponding to an RB whose resourceconfiguration is rejected by the second target base station.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, or the eighth possibleimplementation manner of the first aspect, in a ninth possibleimplementation manner, the second message further includes at least oneof followings:

fourth type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station;

second type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe second type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between thesecond target base station and the source base station; and

third type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe third type of GTP tunnel endpoint information is used for requestinga core network node to convert a GTP tunnel endpoint.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, or the ninth possibleimplementation manner of the first aspect, in a tenth possibleimplementation manner, the handover request acknowledge message includesat least one of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an identifier of an RABaccepted by the second target base station, and a corresponding relationbetween at least one RAB accepted by the first target base stationand/or the second target base station and the first target base stationand/or the second target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, or the tenth possibleimplementation manner of the first aspect, in an eleventh possibleimplementation manner, the first transparent container configurationincludes at least one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, or the eleventh possibleimplementation manner of the first aspect, in a twelfth possibleimplementation manner, the configuration information of the RB includesat least one of followings: configuration information of a PDCP entitycorresponding to the RB, configuration information of at least one RLCentity corresponding to the RB, MAC configuration informationcorresponding to each RLC entity corresponding to the RB, logic channelconfiguration message, physical layer configuration information, anidentifier of a service, split indication information and configurationinformation of a radio resource corresponding to the RB.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, or the twelfth possibleimplementation manner of the first aspect, in a thirteenth possibleimplementation manner, the configuration information of the radioresource corresponding to the RB includes at least one of followings: aphysical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, or the thirteenth possibleimplementation manner of the first aspect, in a fourteenth possibleimplementation manner, the sending, by the first target base station,the handover request acknowledge message to the source base station orthe core network node includes:

sending, by the first target base station, the handover requestacknowledge message to the source base station to trigger the sourcebase station to send a handover command message to the user equipment,so as to enable the user equipment to establish connections with thefirst target base station and the second target base station; or

sending, by the first target base station, the handover requestacknowledge message to the core network node to trigger the core networknode to send a handover request reply message to the source basestation, thereby triggering the source base station to send a handovercommand message to the user equipment, so as to enable the userequipment to establish connection with the first target base station andthe second target base station.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, or the fourteenth possibleimplementation manner of the first aspect, in a fifteenth possibleimplementation manner, after the sending, by the first target basestation, the handover request reply message to the source base stationor the core network node, the method further includes: receiving, by thefirst target base station, a radio resource control RRC connectionreconfiguration completion message sent by the user equipment, andestablishing a connection with the user equipment.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, or the fifteenth possibleimplementation manner of the first aspect, in a sixteenth possibleimplementation manner, after the receiving, by the first target basestation, a radio resource control RRC connection reconfigurationcompletion message sent by the user equipment, the method furtherincludes: sending, by the first target base station, a handoverindication message of the user equipment to the second target basestation, for indicating that the second target base station starts touse a resource configured to the user equipment.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, the fifteenth possibleimplementation manner of the first aspect, or the sixteenth possibleimplementation manner of the first aspect, in a seventeenth possibleimplementation manner, after the sending, by the first target basestation, the handover indication message of the user equipment to thesecond target base station, the method further includes: receiving, bythe first target base station, a handover indication reply message ofthe user equipment sent by the second target base station, wherein thecut-over indication reply message of the user equipment includes thethird type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe third type of GTP tunnel endpoint information is used for requestingthe core network node to switch a GTP tunnel endpoint.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, the fifteenth possibleimplementation manner of the first aspect, the sixteenth possibleimplementation manner of the first aspect, or the seventeenth possibleimplementation manner of the first aspect, in an eighteenth possibleimplementation manner, after the receiving, by the first target basestation, the RRC connection reconfiguration completion message sent bythe user equipment, the method further includes: sending, by the firsttarget base station, a path switch request message to the core networknode to request to hand over a service corresponding to the userequipment in the core network node to the first target base stationand/or the second target base station.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, the fifteenth possibleimplementation manner of the first aspect, the sixteenth possibleimplementation manner of the first aspect, the seventeenth possibleimplementation manner of the first aspect, or the eighteenth possibleimplementation manner of the first aspect, in a nineteenth possibleimplementation manner, the sending, by the first target base station, ahandover request acknowledge message to the source base station or thecore network node, includes: sending, by the first target base station,the handover request acknowledge message to the source base station orthe core network node to trigger the source base station to send dataand/or signaling of the user equipment in the source base station to thefirst target base station and/or the second target base station.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, the fifteenth possibleimplementation manner of the first aspect, the sixteenth possibleimplementation manner of the first aspect, the seventeenth possibleimplementation manner of the first aspect, the eighteenth possibleimplementation manner of the first aspect, or the nineteenth possibleimplementation manner of the first aspect, in a twentieth possibleimplementation manner, the first target base station receives the dataand/or signaling of the user equipment sent by the source base station,and sends corresponding part of the second target base station in thedata and/or signaling of the user equipment to the second target basestation.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, the fifteenth possibleimplementation manner of the first aspect, the sixteenth possibleimplementation manner of the first aspect, the seventeenth possibleimplementation manner of the first aspect, the eighteenth possibleimplementation manner of the first aspect, the nineteenth possibleimplementation manner of the first aspect, or the twentieth possibleimplementation manner, in a twenty-first possible implementation manner,the triggering the source base station to send the data and/or signalingof the user equipment in the source base station to the first targetbase station and/or the second target base station, includes: triggeringthe source base station to send corresponding part of the first targetbase station in the data and/or signaling of the user equipment to thefirst target base station, and send the part corresponding to the secondtarget base station in the data and/or signaling of the user equipmentto the second target base station.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, the fifteenth possibleimplementation manner of the first aspect, the sixteenth possibleimplementation manner of the first aspect, the seventeenth possibleimplementation manner of the first aspect, the eighteenth possibleimplementation manner of the first aspect, the nineteenth possibleimplementation manner of the first aspect, the twentieth possibleimplementation manner, or the twenty-first possible implementationmanner, in a twenty-second possible implementation manner, the dataand/or signaling of the user equipment includes at least one offollowings: data of a service corresponding to the user equipment, whichhas been sent without receiving a reply ACK, data of a servicecorresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN status transfer information and an end marker packet.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, the fifteenth possibleimplementation manner of the first aspect, the sixteenth possibleimplementation manner of the first aspect, the seventeenth possibleimplementation manner of the first aspect, the eighteenth possibleimplementation manner of the first aspect, the nineteenth possibleimplementation manner of the first aspect, the twentieth possibleimplementation manner, the twenty-first possible implementation manner,or the twenty-second possible implementation manner, in a twenty-thirdpossible implementation manner, the end marker packet is used fortriggering the first target base station and/or the second target basestation to receive data sent by a serving gateway in sequence.

In combination with the first aspect, the first possible implementationmanner of the first aspect, the second possible implementation manner ofthe first aspect, the third possible implementation manner of the firstaspect, the fourth possible implementation manner of the first aspect,the fifth possible implementation manner of the first aspect, the sixthpossible implementation manner of the first aspect, the seventh possibleimplementation manner of the first aspect, the eighth possibleimplementation manner of the first aspect, the ninth possibleimplementation manner of the first aspect, the tenth possibleimplementation manner of the first aspect, the eleventh possibleimplementation manner of the first aspect, the twelfth possibleimplementation manner of the first aspect, the thirteenth possibleimplementation manner of the first aspect, the fourteenth possibleimplementation manner of the first aspect, the fifteenth possibleimplementation manner of the first aspect, the sixteenth possibleimplementation manner of the first aspect, the seventeenth possibleimplementation manner of the first aspect, the eighteenth possibleimplementation manner of the first aspect, the nineteenth possibleimplementation manner of the first aspect, the twentieth possibleimplementation manner, the twenty-first possible implementation manner,the twenty-second possible implementation manner, or the twenty-thirdpossible implementation manner, in a twenty-fourth possibleimplementation manner, the receiving, by the first target base station,the handover request message sent by the source base station includes:receiving, by the first target base station, the handover requestmessage, which comes from the source base station, forwarded by the corenetwork node.

In a second aspect, a handover processing method is provided, including:sending, by a first source base station, a handover request message to atarget base station, to make a request for a handover of a userequipment from the first source base station and a second source basestation to the target base station; receiving, by the first source basestation, a handover request acknowledge message sent by the target basestation; and sending, by the first source base station, a handovercommand message to the user equipment, to notify the user equipment tohand over from the first source base station and the second source basestation to the target base station.

In a first possible implementation manner of the second aspect, beforethe sending, by a first source base station, a handover request messageto a target base station, the method further includes: sending, by thefirst source base station, a handover initiation request message to thesecond source base station, to make a request for a handover of the userequipment from the second source base station to the target basestation; and receiving, by the first source base station, a handoverinitiation response message from the second source base station, andgenerating the handover request message according to the handoverinitiation response message.

In combination with the second aspect, or the first possibleimplementation manner of the second aspect, in a second possibleimplementation manner, before the sending, by a first source basestation, a handover request message to a target base station, the methodfurther includes: sending, by the first source base station, a handoverinitiation request message to the second source base station through alocal gateway; and receiving, by the first source base station, thehandover request message from the local gateway, wherein the handoverrequest message is generated by the local gateway according to ahandover initiation response message from the second source basestation.

In combination with the second aspect, the first possible implementationmanner of the second aspect, or the second possible implementationmanner of the second aspect, in a third possible implementation manner,after the receiving, by the first source base station, the handoverrequest acknowledge message sent by the target base station, the methodfurther includes: sending, by the first source base station, a handoverexecution notification message to the second source base station, fornotifying the second source base station to start executing a handoveroperation.

In combination with the second aspect, the first possible implementationmanner of the second aspect, the second possible implementation mannerof the second aspect, or the third possible implementation manner of thesecond aspect, in a fourth possible implementation manner, after thesending, by the first source base station, the handover executionnotification message to the second source base station, the methodfurther includes: receiving, by the first source base station, ahandover execution notification response message sent by the secondsource base station, wherein the handover execution notificationresponse message includes: SN status transfer information correspondingto at least one RAB served by the second source base station, and/or adata packet, in need of forwarding, and corresponding to at least oneRAB served by the second source base station.

In combination with the second aspect, the first possible implementationmanner of the second aspect, the second possible implementation mannerof the second aspect, the third possible implementation manner of thesecond aspect, or the fourth possible implementation manner of thesecond aspect, in a fifth possible implementation manner, the receiving,by the first source base station, a handover request acknowledge messagesent by the target base station includes: receiving, by the first sourcebase station, the handover request acknowledge message sent by thetarget base station for triggering the first source base station and/orthe second source base station to send data and/or signaling of the userequipment to the target base station.

In combination with the second aspect, the first possible implementationmanner of the second aspect, the second possible implementation mannerof the second aspect, the third possible implementation manner of thesecond aspect, the fourth possible implementation manner of the secondaspect, or the fifth possible implementation manner of the secondaspect, in a sixth possible implementation manner, the triggering thefirst source base station and/or the second source base station to sendthe data and/or signaling of the user equipment to the target basestation, includes:

triggering the first source base station to send data and/or signalingof the user equipment in the first target base station and the secondtarget base station to the target base station; or

triggering the first source base station to send data and/or signalingof the user equipment in the first source base station to the targetbase station, and triggering the second source base station to send dataand/or signaling of the user equipment in the second source base stationto the target base station.

In combination with the second aspect, the first possible implementationmanner of the second aspect, the second possible implementation mannerof the second aspect, the third possible implementation manner of thesecond aspect, the fourth possible implementation manner of the secondaspect, the fifth possible implementation manner of the second aspect,or the sixth possible implementation manner of the second aspect, in aseventh possible implementation manner, the data and/or signaling of theuser equipment includes: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data of aservice corresponding to the user equipment with a NACK received, SDUdata, serial number SN status transfer information and an end markerpacket.

In combination with the second aspect, the first possible implementationmanner of the second aspect, the second possible implementation mannerof the second aspect, the third possible implementation manner of thesecond aspect, the fourth possible implementation manner of the secondaspect, the fifth possible implementation manner of the second aspect,the sixth possible implementation manner of the second aspect, or theseventh possible implementation manner of the second aspect, in aneighth possible implementation manner, before the sending, by the firstsource base station, the end marker packet to the target base station,the method further includes: receiving, by the first source basestation, the end marker packet sent by an S-GW.

In combination with the second aspect, the first possible implementationmanner of the second aspect, the second possible implementation mannerof the second aspect, the third possible implementation manner of thesecond aspect, the fourth possible implementation manner of the secondaspect, the fifth possible implementation manner of the second aspect,the sixth possible implementation manner of the second aspect, theseventh possible implementation manner of the second aspect, or theeighth possible implementation manner of the second aspect, in a ninthpossible implementation manner, the sending, by the first source basestation, the handover request message to the target base station,includes: sending, by the first source base station, the handoverrequest message to the target base station through a local gateway.

In a third aspect, a handover processing method is provided, including:sending, by a source base station, a handover request message to a firsttarget base station; receiving, by the source base station, a handoverrequest ackowledge message sent by the first target base station,wherein the handover request ackowledge message is used for notifyingthe source base station to hand over the user equipment to at least onetarget cell of the first target base station and/or at least one targetcell of a second target base station; and sending, by the source basestation, a handover command message to the user equipment, to indicatethe user equipment to hand over to the first target base station and thesecond target base station.

In the first possible implementation manner of the third aspect, thehandover request message includes at least one of followings:information of at least one target cell of the second target basestation, measurement report information of the user equipment, contextinformation of the user equipment and information of a service of theuser equipment, wherein the information of the service includes RABinformation of the service.

In combination with the third aspect, or the first possibleimplementation manner of the third aspect, in the second possibleimplementation manner, the information of the service further includesat least one of followings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

In combination with the third aspect, the first possible implementationmanner of the third aspect, or the second possible implementation mannerof the third aspect, in a third possible implementation manner, the GTPtunnel endpoint information is first type of GTP tunnel endpointinformation or fourth type of GTP tunnel endpoint information, whereinthe first type of GTP tunnel endpoint information is used forestablishing a transmission bearer of an S1 interface between a servinggateway S-GW and the first target base station and/or the second targetbase station, and the fourth type of GTP tunnel endpoint information isused for establishing a transmission bearer for forwarding data betweenthe first target base station and the second target base station.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, or the third possible implementation manner of thethird aspect, in a fourth possible implementation manner, the handoverrequest acknowledge message includes at least one of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation between atleast one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, or the fourth possible implementation manner of the thirdaspect, in a fifth possible implementation manner, the first transparentcontainer configuration includes at least one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station;

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,or the fifth possible implementation manner of the third aspect, in asixth possible implementation manner, the configuration information ofthe RB includes at least one of followings:

configuration information of a PDCP entity corresponding to the RB,configuration information of at least one RLC entity corresponding tothe RB, MAC configuration information corresponding to each RLC entitycorresponding to the RB, logic channel configuration message, physicallayer configuration information, an identifier of a service, splitindication information and configuration information of a radio resourcecorresponding to the RB.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,the fifth possible implementation manner of the third aspect, or thesixth possible implementation manner of the third aspect, in a seventhpossible implementation manner, the configuration information of theradio resource of the RB includes at least one of followings: a physicalcell identifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time slotinformation, time domain information, code domain information and spacedomain information.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,the fifth possible implementation manner of the third aspect, the sixthpossible implementation manner of the third aspect, or the seventhpossible implementation manner of the third aspect, in an eighthpossible implementation manner, the receiving, by the source basestation, the handover request acknowledge message sent by the firsttarget base station, includes: receiving, by the source base station,the handover request acknowledge message from the first target basestation, which is forwarded by a core network element.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,the fifth possible implementation manner of the third aspect, the sixthpossible implementation manner of the third aspect, the seventh possibleimplementation manner of the third aspect, or the eighth possibleimplementation manner of the third aspect, in a ninth possibleimplementation manner, after the receiving, by the source base station,the handover request acknowledge message sent by the first target basestation, the method further includes: sending, by the source basestation, data and/or signaling of the user equipment to the first targetbase station and/or the second target base station.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,the fifth possible implementation manner of the third aspect, the sixthpossible implementation manner of the third aspect, the seventh possibleimplementation manner of the third aspect, the eighth possibleimplementation manner of the third aspect, or the ninth possibleimplementation manner of the third aspect, in a tenth possibleimplementation manner, after the sending, by the source base station,the handover command message to the user equipment, the method furtherincludes: sending, by the source base station, data and/or signaling ofthe user equipment to the first target base station and/or the secondtarget base station.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,the fifth possible implementation manner of the third aspect, the sixthpossible implementation manner of the third aspect, the seventh possibleimplementation manner of the third aspect, the eighth possibleimplementation manner of the third aspect, the ninth possibleimplementation manner of the third aspect, or the tenth possibleimplementation manner of the third aspect, in an eleventh possibleimplementation manner, the sending, by the source base station, the dataand/or signaling of the user equipment to the first target base stationand/or the second target base station includes:

sending, by the source base station, the data and/or signaling of theuser equipment to the first target base station, for enabling the firsttarget base station to send corresponding part of the second target basestation in the data and/or signaling of the user equipment to the secondtarget base station; or

sending, by the source base station, corresponding part of the firsttarget base station in the data and/or signaling of the user equipmentto the first target base station, and sending corresponding part of thesecond target base station in the data and/or signaling of the userequipment to the second target base station.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,the fifth possible implementation manner of the third aspect, the sixthpossible implementation manner of the third aspect, the seventh possibleimplementation manner of the third aspect, the eighth possibleimplementation manner of the third aspect, the ninth possibleimplementation manner of the third aspect, the tenth possibleimplementation manner of the third aspect, or the eleventh possibleimplementation manner of the third aspect, in a twelfth possibleimplementation manner, the data and/or signaling of the user equipmentcomprises at least one of followings: data of a service corresponding tothe user equipment, which has been sent without receiving a reply ACK,data of the service corresponding to the user equipment, of which aresponse of non-acknowledgement NACK is received, data of service dataunit SDU, serial number SN status transfer information and an end markerpacket.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,the fifth possible implementation manner of the third aspect, the sixthpossible implementation manner of the third aspect, the seventh possibleimplementation manner of the third aspect, the eighth possibleimplementation manner of the third aspect, the ninth possibleimplementation manner of the third aspect, the tenth possibleimplementation manner of the third aspect, the eleventh possibleimplementation manner of the third aspect, or the twelfth possibleimplementation manner of the third aspect, in a thirteenth possibleimplementation manner, the end marker packet is used for triggering thefirst target base station and/or the second target base station toreceive data sent by a serving gateway in sequence.

In combination with the third aspect, the first possible implementationmanner of the third aspect, the second possible implementation manner ofthe third aspect, the third possible implementation manner of the thirdaspect, the fourth possible implementation manner of the third aspect,the fifth possible implementation manner of the third aspect, the sixthpossible implementation manner of the third aspect, the seventh possibleimplementation manner of the third aspect, the eighth possibleimplementation manner of the third aspect, the ninth possibleimplementation manner of the third aspect, the tenth possibleimplementation manner of the third aspect, the eleventh possibleimplementation manner of the third aspect, the twelfth possibleimplementation manner of the third aspect, or the thirteenth possibleimplementation manner of the third aspect, in a fourteenth possibleimplementation manner, the sending, by a source base station, thehandover request message to a first target base station, includes:sending, by the source base station, the handover request message to thefirst target base station through a core network node.

In a fourth aspect, a handover processing method is provided, including:receiving, by a target base station, a handover request message sent bya first source base station, wherein the handover request message isused for making a request for a handover of a user equipment from thefirst source base station and a second source base station to the targetbase station; and sending, by the target base station, a handoverrequest acknowledge message to the first source base station, whereinthe handover request acknowledge message is used for indicating that thetarget base station accepts the handover of the user equipment from thefirst source base station and the second source base station to thetarget base station.

In a first possible implementation manner of the fourth aspect, afterthe sending, by the target base station, the handover requestacknowledge message to the first source base station, the method furtherincludes: receiving, by the target base station, data and/or signalingof the user equipment sent by the first source base station and/or thesecond source base station.

In combination with the fourth aspect, or the first possibleimplementation manner of the fourth aspect, in a second possibleimplementation manner, the receiving, by the target base station, dataand/or signaling of the user equipment sent by the first source basestation and/or the second source base station includes:

receiving, by the target base station, the data and/or signaling of theuser equipment sent by the first source base station, and/or receivingthe data and/or signaling of the user equipment sent by the secondsource base station; or

receiving, by the target base station, the data and/or signaling of theuser equipment corresponding to the first source base station and/or thesecond source base station, sent by the first source base station.

In combination with the fourth aspect, the first possible implementationmanner of the fourth aspect, or the second possible implementationmanner of the fourth aspect, in a third possible implementation manner,the data and/or signaling of the user equipment comprises at least oneof followings: data of a service corresponding to the user equipment,which has been sent without receiving a reply ACK, data of a servicecorresponding to the user equipment with a NACK received, SDU data,serial number SN status transfer information and an end marker packet.

In combination with the fourth aspect, the first possible implementationmanner of the fourth aspect, the second possible implementation mannerof the fourth aspect, or the third possible implementation manner of thefourth aspect, in a fourth possible implementation manner, thereceiving, by a target base station, the handover request message sentby a first source base station comprises: receiving, by the target basestation, the handover request message, which comes from the first sourcebase station, forwarded by a local gateway.

In combination with the fourth aspect, the first possible implementationmanner of the fourth aspect, the second possible implementation mannerof the fourth aspect, the third possible implementation manner of thefourth aspect, or the fourth possible implementation manner of thefourth aspect, in a fifth possible implementation manner, after thesending, by the target base station, the handover request acknowledgemessage to the first source base station, the method further includes:receiving, by the target base station, a radio resource control RRCconnection reconfiguration completion message sent by the userequipment, and establishing a connection with the user equipment.

In a fifth aspect, a base station is provided, the base station is afirst target base station, the first target base station includes: areceiving unit, configured to receive a handover request message sent bya source base station or a core network node; a sending unit, configuredto send, according to the handover request message, a first message to asecond target base station to notify the second target base station thata handover of part or all of a service of a user equipment to the secondtarget base station is to be performed, wherein the sending unit isfurther configured to send a handover request acknowledge message to thesource base station or the core network node, wherein the handoverrequest acknowledge message is used for notifying the source basestation or the core network node to hand over the user equipment to atleast one target cell of the first target base station and/or at leastone target cell of the second target base station.

In a first possible implementation manner of the fifth aspect, thesending unit is configured to realize the sending, according to thehandover request message, the first message to the second target basestation in a following manner: determining, according to a measurementreport of the user equipment and/or radio access bear RAB information ofthe user equipment in the handover request message, that the handover ofthe part or all of the service of the user equipment to a target cell ofthe second target base station; or determining, according to informationof a target cell of the second target base station in the handoverrequest message, that the handover of the part or all of the service ofthe user equipment to the second target base station; and sending thefirst message to the second target base station.

In combination with the fifth aspect or the first possibleimplementation manner of the fifth aspect, in a second possibleimplementation manner, the handover request message includes at leastone of followings: information of at least one target cell of the secondtarget base station, measurement report information of the userequipment, context information of the user equipment and information ofa service of the user equipment, wherein the information of the serviceincludes RAB information of the service.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, or the second possible implementation mannerof the fifth aspect, in a third possible implementation manner, thefirst message includes: information of at least one service of the userequipment, wherein the information of the service includes RABinformation of the service and/or configuration information of a radiobear RB.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, or the third possible implementation manner of thefifth aspect, in a fourth possible implementation manner, theinformation of the service further includes at least one of followings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information;

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, or the fourth possible implementation manner of the fifthaspect, in a fifth possible implementation manner, the GTP tunnelendpoint information is first type of GTP tunnel endpoint information orfourth type of GTP tunnel endpoint information, wherein the first typeof GTP tunnel endpoint information is used for establishing atransmission bearer of an S1 interface between a serving gateway S-GWand the first target base station and/or the second target base station,and the fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,or the fifth possible implementation manner of the fifth aspect, in asixth possible implementation manner, the configuration information ofthe RB includes: configuration information of a packet data convergenceprotocol PDCP layer, a radio link control RLC layer, a medium accesscontrol MAC layer and a physical layer; or configuration information ofan RLC layer, an MAC layer and a physical layer.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, or thesixth possible implementation manner of the fifth aspect, in a seventhpossible implementation manner, the receiving unit is further configuredto receive a second message sent by the second target base station afterthe first target base station sends the first message to the secondtarget base station, wherein the second message is used for indicatinginformation regarding whether the handover of the part or all of theservice of the user equipment to the second target base station isaccepted by the second base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, or the seventhpossible implementation manner of the fifth aspect, in an eighthpossible implementation manner, the second message comprises at leastone of followings: an identifier of the user equipment, firstinformation and indication information, wherein the indicationinformation includes at least one of followings: indication informationof refusing the handover of the part or all of the service of the userequipment to the second target base station, indication information ofaccepting the handover of the part or all of the service of the userequipment to the second target base station, and indication informationof modifying the first message; the first information includes at leastone of followings: an identifier of an RB accepted by the second targetbase station, configuration information of an RB accepted by the secondtarget base station, an identifier of an RAB corresponding to an RBaccepted by the second target base station, an identifier of an RB whoseresource configuration is rejected by the second target base station,and an identifier of an RAB corresponding to an RB whose resourceconfiguration is rejected by the second target base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, or the eighth possibleimplementation manner of the fifth aspect, in a ninth possibleimplementation manner, the second message further includes at least oneof followings:

fourth type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station;

second type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe second type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between thesecond target base station and the source base station; and

third type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe third type of GTP tunnel endpoint information is used for requestinga core network node to convert a GTP tunnel endpoint.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, or the ninth possibleimplementation manner of the fifth aspect, in a tenth possibleimplementation manner, the handover request acknowledge message includesat least one of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation between atleast one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, or the tenth possibleimplementation manner of the fifth aspect, in an eleventh possibleimplementation manner, the first transparent container configurationincludes at least one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, or the eleventh possibleimplementation manner of the fifth aspect, in a twelfth possibleimplementation manner, the configuration information of the RB includesat least one of followings: configuration information of a PDCP entitycorresponding to the RB, configuration information of at least one RLCentity corresponding to the RB, MAC configuration informationcorresponding to each RLC entity corresponding to the RB, logic channelconfiguration message, physical layer configuration information, anidentifier of a service, split indication information and configurationinformation of a radio resource corresponding to the RB.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, or the twelfth possibleimplementation manner of the fifth aspect, in s thirteenth possibleimplementation manner, the configuration information of the radioresource corresponding to the RB includes at least one of followings: aphysical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, or the thirteenth possibleimplementation manner of the fifth aspect, in a fourteenth possibleimplementation manner, the sending unit is configured to realize thesending the handover request acknowledge message to the source basestation or the core network node in a following manner:

sending the handover request acknowledge message to the source basestation to trigger the source base station to send a handover commandmessage to the user equipment, so as to enable the user equipment toestablish connections with the first target base station and the secondtarget base station; or

sending the handover request acknowledge message to the core networknode to trigger the core network node to send the handover requestacknowledge message to the source base station, thereby triggering thesource base station to send a handover command message to the userequipment, so as to enable the user equipment to establish connectionswith the first target base station and the second target base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, or the fourteenth possibleimplementation manner of the fifth aspect, in a fifteenth possibleimplementation manner, the receiving unit is further configured toreceive a radio resource control RRC connection reconfigurationcompletion message sent by the user equipment, and control the firsttarget base station to establish a connection with the user equipment.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, or the fifteenth possibleimplementation manner of the fifth aspect, in a sixteenth possibleimplementation manner, the sending unit is further configured to send,after the first target base station receives the RRC connectionreconfiguration completion message sent by the user equipment, ahandover indication message of the user equipment to the second targetbase station, for indicating that the second target base station startsto use a resource configured to the user equipment.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, the fifteenth possibleimplementation manner of the fifth aspect, or the sixteenth possibleimplementation manner of the fifth aspect, in a seventeenth possibleimplementation manner, the receiving unit is further configured toreceive, after the first target base station sends the handoverindication message of the user equipment to the second target basestation, a handover indication reply message of the user equipment sentby the second target base station, wherein the handover indication replymessage of the user equipment comprises: third type of GTP tunnelendpoint information corresponding to an identifier of an RAB acceptedby the second target base station, wherein the third type of GTP tunnelendpoint information is used for requesting the core network node toswitch a GTP tunnel endpoint.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, the fifteenth possibleimplementation manner of the fifth aspect, the sixteenth possibleimplementation manner of the fifth aspect, or the seventeenth possibleimplementation manner of the fifth aspect, in an eighteenth possibleimplementation manner, the sending unit is further configured to send,after the first target base station receives the RRC connectionreconfiguration completion message sent by the user equipment, a pathswitch request message to the core network node to request to hand overa service corresponding to the user equipment in the core network nodeto the first target base station and/or the second target base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, the fifteenth possibleimplementation manner of the fifth aspect, the sixteenth possibleimplementation manner of the fifth aspect, the seventeenth possibleimplementation manner of the fifth aspect, or the eighteenth possibleimplementation manner of the fifth aspect, in a nineteenth possibleimplementation manner, the sending unit is configured to realize thesending the handover request acknowledge message to the source basestation or the core network node in a following manner: sending thehandover request acknowledge message to the source base station or thecore network node to trigger the source base station to send data and/orsignaling of the user equipment in the source base station to the firsttarget base station and/or the second target base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, the fifteenth possibleimplementation manner of the fifth aspect, the sixteenth possibleimplementation manner of the fifth aspect, the seventeenth possibleimplementation manner of the fifth aspect, the eighteenth possibleimplementation manner of the fifth aspect, or the nineteenth possibleimplementation manner of the fifth aspect, in a twentieth possibleimplementation manner, the receiving unit is further configured toreceive the data and/or signaling of the user equipment sent by thesource base station; and the sending unit is further configured to sendcorresponding part of the second target base station in the data and/orsignaling of the user equipment to the second target base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, the fifteenth possibleimplementation manner of the fifth aspect, the sixteenth possibleimplementation manner of the fifth aspect, the seventeenth possibleimplementation manner of the fifth aspect, the eighteenth possibleimplementation manner of the fifth aspect, the nineteenth possibleimplementation manner of the fifth aspect, or the twentieth possibleimplementation manner, in a twenty-first possible implementation manner,the triggering the source base station to send the data and/or signalingof the user equipment in the source base station to the first targetbase station and/or the second target base station, comprises:triggering the source base station to send corresponding part of thefirst target base station in the data and/or signaling of the userequipment to the first target base station, and to send correspondingpart of the second target base station in the data and/or signaling ofthe user equipment to the second target base station.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, the fifteenth possibleimplementation manner of the fifth aspect, the sixteenth possibleimplementation manner of the fifth aspect, the seventeenth possibleimplementation manner of the fifth aspect, the eighteenth possibleimplementation manner of the fifth aspect, the nineteenth possibleimplementation manner of the fifth aspect, the twentieth possibleimplementation manner, or the twenty-first possible implementationmanner, in a twenty-second possible implementation manner, the dataand/or signaling of the user equipment comprise(s) at least one offollowings: data of a service corresponding to the user equipment, whichhas been sent without receiving a reply ACK, data of the servicecorresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN status transfer information and an end marker packet.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, the fifteenth possibleimplementation manner of the fifth aspect, the sixteenth possibleimplementation manner of the fifth aspect, the seventeenth possibleimplementation manner of the fifth aspect, the eighteenth possibleimplementation manner of the fifth aspect, the nineteenth possibleimplementation manner of the fifth aspect, the twentieth possibleimplementation manner, the twenty-first possible implementation manner,or the twenty-second possible implementation manner, in a twenty-thirdpossible implementation manner, the end marker packet is used fortriggering the first target base station and/or the second target basestation to receive data sent by a serving gateway in sequence.

In combination with the fifth aspect, the first possible implementationmanner of the fifth aspect, the second possible implementation manner ofthe fifth aspect, the third possible implementation manner of the fifthaspect, the fourth possible implementation manner of the fifth aspect,the fifth possible implementation manner of the fifth aspect, the sixthpossible implementation manner of the fifth aspect, the seventh possibleimplementation manner of the fifth aspect, the eighth possibleimplementation manner of the fifth aspect, the ninth possibleimplementation manner of the fifth aspect, the tenth possibleimplementation manner of the fifth aspect, the eleventh possibleimplementation manner of the fifth aspect, the twelfth possibleimplementation manner of the fifth aspect, the thirteenth possibleimplementation manner of the fifth aspect, the fourteenth possibleimplementation manner of the fifth aspect, the fifteenth possibleimplementation manner of the fifth aspect, the sixteenth possibleimplementation manner of the fifth aspect, the seventeenth possibleimplementation manner of the fifth aspect, the eighteenth possibleimplementation manner of the fifth aspect, the nineteenth possibleimplementation manner of the fifth aspect, the twentieth possibleimplementation manner, the twenty-first possible implementation manner,the twenty-second possible implementation manner, or the twenty-thirdpossible implementation manner, in a twenty-fourth possibleimplementation manner, the receiving unit is configured to realize thereceiving the handover request message sent by the source base stationin a following manner: receiving the handover request message, whichcomes from the source base station, forwarded by the core network node.

In a sixth aspect, a base station is provided, the base station is afirst source base station, the source base station includes: a sendingunit, configured to send a handover request message to a target basestation, to make a request for a handover of a user equipment from thefirst source base station and a second source base station to the targetbase station; and a receiving unit, configured to receive a handoverrequest acknowledge message sent by the target base station, wherein thesending unit is further configured to send a handover command message tothe user equipment, and notify the user equipment to hand over from thefirst source base station and the second source base station to thetarget base station.

In a first possible implementation manner of the sixth aspect, thesending unit is further configured to send, before the first source basestation sends the handover request message to the target base station, ahandover initiation request message to the second source base station,to make a request for a handover of the user equipment from the secondsource base station to the target base station; and the receiving unitis further configured to receive a handover initiation response messagefrom the second source base station, and generating the handover requestmessage according to the handover initiation response message.

In combination with the sixth aspect, or the first possibleimplementation manner of the sixth aspect, in a second possibleimplementation manner, the sending unit is further configured to send,before the first source base station sends the handover request messageto the target base station, a handover initiation request message to thesecond source base station through a local gateway; and the receivingunit is further configured to receive the handover request message fromthe local gateway, wherein the handover request message is generated bythe local gateway according to a handover initiation response messagefrom the second source base station.

In combination with the sixth aspect, the first possible implementationmanner of the sixth aspect, or the second possible implementation mannerof the sixth aspect, in a third possible implementation manner, thesending unit is further configured to send, after the first source basestation receives the handover request acknowledge message sent by thetarget base station, a handover execution notification message to thesecond source base station, for notifying the second source base stationto start executing a handover operation.

In combination with the sixth aspect, the first possible implementationmanner of the sixth aspect, the second possible implementation manner ofthe sixth aspect, or the third possible implementation manner of thesixth aspect, in a fourth possible implementation manner, the receivingunit is further configured to receive a handover execution notificationresponse message sent by the second source base station, wherein thehandover execution notification response message comprises: SN statustransfer information corresponding to at least one RAB served by thesecond source base station, and/or a data packet, in need of forwarding,corresponding to at least one RAB served by the second source basestation.

In combination with the sixth aspect, the first possible implementationmanner of the sixth aspect, the second possible implementation manner ofthe sixth aspect, the third possible implementation manner of the sixthaspect, or the fourth possible implementation manner of the sixthaspect, in a fifth possible implementation manner, the receiving unit isfurther configured to receive the handover request acknowledge messagesent by the target base station for triggering the first source basestation and/or the second source base station to send data and/orsignaling of the user equipment to the target base station.

In combination with the sixth aspect, the first possible implementationmanner of the sixth aspect, the second possible implementation manner ofthe sixth aspect, the third possible implementation manner of the sixthaspect, the fourth possible implementation manner of the sixth aspect,or the fifth possible implementation manner of the sixth aspect, in asixth possible implementation manner, the triggering the first sourcebase station and/or the second source base station to send the dataand/or signaling of the user equipment to the target base stationincludes:

triggering the first source base station to send data and/or signalingof the user equipment in the first target base station and the secondtarget base station to the target base station; or

triggering the first source base station to send the data and/orsignaling of the user equipment in the first source base station to thetarget base station, and triggering the second source base station tosend data and/or signaling of the user equipment in the second sourcebase station to the target base station.

In combination with the sixth aspect, the first possible implementationmanner of the sixth aspect, the second possible implementation manner ofthe sixth aspect, the third possible implementation manner of the sixthaspect, the fourth possible implementation manner of the sixth aspect,the fifth possible implementation manner of the sixth aspect, or thesixth possible implementation manner of the sixth aspect, in a seventhpossible implementation manner, the data and/or signaling of the userequipment comprise(s) at least one of followings: data of a servicecorresponding to the user equipment which has been sent withoutreceiving a reply ACK, data of the service corresponding to the userequipment with a NACK received, SDU data, serial number SN statustransfer information and an end marker packet.

In combination with the sixth aspect, the first possible implementationmanner of the sixth aspect, the second possible implementation manner ofthe sixth aspect, the third possible implementation manner of the sixthaspect, the fourth possible implementation manner of the sixth aspect,the fifth possible implementation manner of the sixth aspect, the sixthpossible implementation manner of the sixth aspect, or the seventhpossible implementation manner of the sixth aspect, in an eighthpossible implementation manner, the receiving unit is further configuredto receive, before the first source base station sends the end markerpacket to the target base station, the end marker packet sent by anS-GW.

In combination with the sixth aspect, the first possible implementationmanner of the sixth aspect, the second possible implementation manner ofthe sixth aspect, the third possible implementation manner of the sixthaspect, the fourth possible implementation manner of the sixth aspect,the fifth possible implementation manner of the sixth aspect, the sixthpossible implementation manner of the sixth aspect, the seventh possibleimplementation manner of the sixth aspect, or the eighth possibleimplementation manner of the sixth aspect, in a ninth possibleimplementation manner, the sending unit is further configured to sendthe handover request message to the target base station through a localgateway.

In a seventh aspect, a base station is provided, the base station is asource base station, the source base station includes: a sending unit,configured to send a handover request message to a first target basestation; and a receiving unit, configured to receive a handover requestacknowledge message sent by the first target base station, wherein thehandover request acknowledge message is used for notifying the sourcebase station to hand over the user equipment to at least one target cellof the first target base station and/or at least one target cell of thesecond target base station, wherein the sending unit is furtherconfigured to send a handover command message to the user equipment, toindicate the user equipment to hand over to the first target basestation and the second target base station.

In a first possible implementation manner of the seventh aspect, thehandover request message includes at least one of followings:information of at least one target cell of the second target basestation, measurement report information of the user equipment, contextinformation of the user equipment and information of a service of theuser equipment, wherein the information of the service includes RABinformation of the service.

In combination with the seventh aspect, or the first possibleimplementation manner of the seventh aspect, in a second possibleimplementation manner, the information of the service further includesat least one of followings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, or the second possibleimplementation manner of the seventh aspect, in a third possibleimplementation manner, the GTP tunnel endpoint information is first typeof GTP tunnel endpoint information or fourth type of GTP tunnel endpointinformation, wherein the first type of GTP tunnel endpoint informationis used for establishing a transmission bearer of an S1 interfacebetween a serving gateway S-GW and the first target base station and/orthe second target base station, and the fourth type of GTP tunnelendpoint information is used for establishing a transmission bearer forforwarding data between the first target base station and the secondtarget base station.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, or the third possibleimplementation manner of the seventh aspect, in a fourth possibleimplementation manner, the handover request acknowledge message includesat least one of followings: an identifier of the user equipmentallocated at the source base station, an identifier of the userequipment allocated at the first target base station and/or the secondtarget base station, a first transparent container configuration, anidentifier of at least one RAB rejected by the first target base stationand/or the second target base station, an identifier of at least one RABaccepted by the first target base station, fifth type of GTP tunnelendpoint information corresponding to an identifier of at least one RABaccepted by the first target base station, an identifier of at least oneRAB accepted by the second target base station, sixth type of GTP tunnelendpoint information corresponding to an identifier of at least one RABaccepted by the second target base station, second type of GTP tunnelendpoint information corresponding to an identifier of an RAB acceptedby the second target base station, and a corresponding relation betweenat least one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; the second type of GTP tunnel endpoint informationis used for establishing a transmission bearer for data forwardingbetween the second target base station and the source base station.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, or the fourth possibleimplementation manner of the seventh aspect, in a fifth possibleimplementation manner, the first transparent container configurationincludes at least one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, or the fifth possibleimplementation manner of the seventh aspect, in a sixth possibleimplementation manner, the configuration information of the RB includesat least one of followings: configuration information of a PDCP entitycorresponding to the RB, configuration information of at least one RLCentity corresponding to the RB, MAC configuration informationcorresponding to each RLC entity corresponding to the RB, logic channelconfiguration message, physical layer configuration information, anidentifier of a service, split indication information and configurationinformation of a radio resource corresponding to the RB.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, the fifth possibleimplementation manner of the seventh aspect, or the sixth possibleimplementation manner of the seventh aspect, in a seventh possibleimplementation manner, the configuration information of the radioresource of the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time slotinformation, time domain information, code domain information and spacedomain information.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, the fifth possibleimplementation manner of the seventh aspect, the sixth possibleimplementation manner of the seventh aspect, or the seventh possibleimplementation manner of the seventh aspect, in an eighth possibleimplementation manner, wherein the receiving unit is configured torealize the receiving the handover request acknowledge message sent bythe first target base station in a following manner: receiving thehandover request acknowledge message from the first target base station,which is forwarded by a core network element

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, the fifth possibleimplementation manner of the seventh aspect, the sixth possibleimplementation manner of the seventh aspect, the seventh possibleimplementation manner of the seventh aspect, or the eighth possibleimplementation manner of the seventh aspect, in a ninth possibleimplementation manner, the sending unit is configured to send, after thesource base station receives the handover request acknowledge messagesent by the first target base station, data and/or signaling of the userequipment to the first target base station and/or the second target basestation.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, the fifth possibleimplementation manner of the seventh aspect, the sixth possibleimplementation manner of the seventh aspect, the seventh possibleimplementation manner of the seventh aspect, the eighth possibleimplementation manner of the seventh aspect, or the ninth possibleimplementation manner of the seventh aspect, in a tenth possibleimplementation manner, the sending unit is configured to send, after thesource base station sends the handover command message to the userequipment, data and/or signaling of the user equipment to the firsttarget base station and/or the second target base station.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, the fifth possibleimplementation manner of the seventh aspect, the sixth possibleimplementation manner of the seventh aspect, the seventh possibleimplementation manner of the seventh aspect, the eighth possibleimplementation manner of the seventh aspect, the ninth possibleimplementation manner of the seventh aspect, or the tenth possibleimplementation manner of the seventh aspect, in an eleventh possibleimplementation manner, the sending unit is configured to realize thesending the data and/or signaling of the user equipment to the firsttarget base station and/or the second target base station in a followingmanner:

sending the data and/or signaling of the user equipment to the firsttarget base station, for enabling the first target base station to sendcorresponding part of the second target base station in the data and/orsignaling of the user equipment to the second target base station; or

sending corresponding part of the first target base station in the dataand/or signaling of the user equipment to the first target base station,and sending corresponding part of the second target base station in thedata and/or signaling of the user equipment to the second target basestation.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, the fifth possibleimplementation manner of the seventh aspect, the sixth possibleimplementation manner of the seventh aspect, the seventh possibleimplementation manner of the seventh aspect, the eighth possibleimplementation manner of the seventh aspect, the ninth possibleimplementation manner of the seventh aspect, the tenth possibleimplementation manner of the seventh aspect, or the eleventh possibleimplementation manner of the seventh aspect, in a twelfth possibleimplementation manner, the data and/or signaling of the user equipmentcomprise(s) at least one of followings: data of a service correspondingto the user equipment, which has been sent without receiving a replyACK, data of the service corresponding to the user equipment, of which aresponse of non-acknowledgement NACK is received, data of service dataunit SDU, serial number SN status transfer information and an end markerpacket.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, the fifth possibleimplementation manner of the seventh aspect, the sixth possibleimplementation manner of the seventh aspect, the seventh possibleimplementation manner of the seventh aspect, the eighth possibleimplementation manner of the seventh aspect, the ninth possibleimplementation manner of the seventh aspect, the tenth possibleimplementation manner of the seventh aspect, the eleventh possibleimplementation manner of the seventh aspect, or the twelfth possibleimplementation manner of the seventh aspect, in a thirteenth possibleimplementation manner, the end marker packet is used for triggering thefirst target base station and/or the second target base station toreceive data sent by a serving gateway in sequence.

In combination with the seventh aspect, the first possibleimplementation manner of the seventh aspect, the second possibleimplementation manner of the seventh aspect, the third possibleimplementation manner of the seventh aspect, the fourth possibleimplementation manner of the seventh aspect, the fifth possibleimplementation manner of the seventh aspect, the sixth possibleimplementation manner of the seventh aspect, the seventh possibleimplementation manner of the seventh aspect, the eighth possibleimplementation manner of the seventh aspect, the ninth possibleimplementation manner of the seventh aspect, the tenth possibleimplementation manner of the seventh aspect, the eleventh possibleimplementation manner of the seventh aspect, the twelfth possibleimplementation manner of the seventh aspect, or the thirteenth possibleimplementation manner of the seventh aspect, in a fourteenth possibleimplementation manner, the sending unit is configured to realize thesending the handover request message to the first target base station ina following manner: sending the handover request message to the firsttarget base station through a core network node.

In an eighth aspect, a base station is provided, the base station is atarget base station, the target base station includes: a receiving unit,configured to receive a handover request message sent by a first sourcebase station, wherein the handover request message is used for making arequest for a handover of a user equipment from the first source basestation and a second source base station to the target base station; anda sending unit, configured to send a handover request acknowledgemessage to the first source base station, wherein the handover requestacknowledge message is used for indicating that the handover of the userequipment from the first source base station and the second source basestation to the target base station is accepted.

In a first possible implementation manner of the eighth aspect, thesending unit is further configured to receive, after the target basestation sends the handover request acknowledge message to the firstsource base station, data and/or signaling of the user equipment sent bythe first source base station and/or the second source base station.

In combination with the eighth aspect, or the first possibleimplementation manner of the eighth aspect, in a second possibleimplementation manner, the receiving unit is configured to realize thatthe target base station to receives the data and/or signaling of theuser equipment sent by the first source base station and/or the secondsource base station in a following manner:

receiving the data and/or signaling of the user equipment sent by thefirst source base station, and/or receiving the data and/or signaling ofthe user equipment sent by the second source base station; or

receiving the data and/or signaling of the user equipment correspondingto the first source base station and/or the second source base station,sent by the first source base station.

In combination with the eighth aspect, the first possible implementationmanner of the eighth aspect, or the second possible implementationmanner of the eighth aspect, in a third possible implementation manner,the data and/or signaling of the user equipment comprises at least oneof followings: data of a service corresponding to the user equipment,which has been sent without receiving a reply ACK, data of a servicecorresponding to the user equipment with a NACK received, SDU data,serial number SN status transfer information and an end marker packet.

In combination with the eighth aspect, the first possible implementationmanner of the eighth aspect, the second possible implementation mannerof the eighth aspect, or the third possible implementation manner of theeighth aspect, in a fourth possible implementation manner, the receivingunit is configured to realize the receiving the handover request messagesent by the first source base station in a following manner: receivingthe handover request message, which comes from the first source basestation, forwarded by a local gateway.

In combination with the eighth aspect, the first possible implementationmanner of the eighth aspect, the second possible implementation mannerof the eighth aspect, the third possible implementation manner of theeighth aspect, or the fourth possible implementation manner of theeighth aspect, in a fifth possible implementation manner, the receivingunit is further configured to receive, after the target base stationsends the handover request acknowledge message to the first source basestation, a radio resource control RRC connection reconfigurationcompletion message sent by the user equipment, and control the targetbase station to establish connection with the user equipment.

In a ninth aspect, a base station is provided, the base station is afirst target base station, the first target base station includes: areceiver, configured to receive a handover request message sent by asource base station or a core network node; and a transmitter,configured to send, according to the handover request message, a firstmessage to a second target base station to notify the second target basestation that a handover of part or all of a service of a user equipmentto the second target base station is to be performed, wherein thetransmitter is further configured to send a handover request acknowledgemessage to the source base station or the core network node, wherein thehandover request acknowledge message is used for notifying the sourcebase station or the core network node to hand over the user equipment toat least one target cell of the first target base station and/or atleast one target cell of the second target base station.

In a first possible implementation manner of the ninth aspect, the firsttarget base station further includes: a processor, wherein the processoris configured to determine, according to a measurement report of theuser equipment and/or radio access bear RAB information of the userequipment in the handover request message, that the handover of the partor all of the service of the user equipment to a target cell of thesecond target base station; or determine, according to information of atarget cell of the second target base station in the handover requestmessage, that the handover of the part or all of a service of the userequipment to the second target base station; and the transmitter isfurther configured to send the first message to the second target basestation.

In combination with the ninth aspect or the first possibleimplementation manner of the ninth aspect, in a second possibleimplementation manner, the handover request message includes at leastone of followings: information of at least one target cell of the secondtarget base station, measurement report information of the userequipment, context information of the user equipment and information ofa service of the user equipment, wherein the information of the serviceincludes RAB information of the service.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, or the second possible implementation mannerof the ninth aspect, in a third possible implementation manner, thefirst message includes information of at least one service of the userequipment, wherein the information of the service includes RABinformation of the service and/or configuration information of a radiobear RB.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, or the third possible implementation manner of theninth aspect, in a fourth possible implementation manner, theinformation of the service further includes at least one of followings:configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information, wherein theconfiguration coordination information of the radio resource of the RBincludes at least one of followings: a physical cell identifier, a logiccell identifier, a virtual cell identifier, frequency information,carrier information, radio resource block information, subcarrierinformation, sub-frame information, time domain information, code domaininformation and space domain information; the split indicationinformation includes data split information based on an RB or data splitinformation based on a packet.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, or the fourth possible implementation manner of the ninthaspect, in a fifth possible implementation manner, the GTP tunnelendpoint information is first type of GTP tunnel endpoint information orfourth type of GTP tunnel endpoint information, wherein the first typeof GTP tunnel endpoint information is used for establishing atransmission bearer of an S1 interface between a serving gateway S-GWand the first target base station and/or the second target base station,and the fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,or the fifth possible implementation manner of the ninth aspect, in asixth possible implementation manner, the configuration information ofthe RB includes: configuration information of a packet data convergenceprotocol PDCP layer, a radio link control RLC layer, a medium accesscontrol MAC layer and a physical layer; or configuration information ofan RLC layer, an MAC layer and a physical layer.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, or thesixth possible implementation manner of the ninth aspect, in a seventhpossible implementation manner, the receiver is further configured toreceive a second message sent by the second target base station afterthe first target base station sends the first message to the secondtarget base station, wherein the second message is used for indicatinginformation regarding whether the handover of the part or all of theservice of the user equipment to the second target base station isaccepted by the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, or the seventhpossible implementation manner of the ninth aspect, in an eighthpossible implementation manner, the second message comprises at leastone of followings: an identifier of the user equipment, firstinformation and indication information, wherein the indicationinformation includes at least one of followings: indication informationof refusing the handover of the part or all of the service of the userequipment to the second target base station, indication information ofaccepting the handover of the part or all of the service of the userequipment to the second target base station, and indication informationof modifying the first message; the first information includes at leastone of followings: an identifier of an RB accepted by the second targetbase station, configuration information of an RB accepted by the secondtarget base station, an identifier of an RAB corresponding to an RBaccepted by the second target base station, an identifier of an RB whoseresource configuration is rejected by the second target base station,and an identifier of an RAB corresponding to an RB whose resourceconfiguration is rejected by the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, or the eighth possibleimplementation manner of the ninth aspect, in a ninth possibleimplementation manner, the second message further includes at least oneof followings:

fourth type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station;

second type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe second type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between thesecond target base station and the source base station; and

third type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe third type of GTP tunnel endpoint information is used for requestinga core network node to convert a GTP tunnel endpoint.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, or the ninth possibleimplementation manner of the ninth aspect, in a tenth possibleimplementation manner, the handover request reply message includes atleast one of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation of at least oneRAB accepted by the first target base station and/or the second targetbase station and the first target base station and/or the second targetbase station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, or the tenth possibleimplementation manner of the ninth aspect, in an eleventh possibleimplementation manner, the first transparent container configurationincludes at least one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, or the eleventh possibleimplementation manner of the ninth aspect, in a twelfth possibleimplementation manner, the configuration information of the RB includesat least one of followings:

configuration information of a PDCP entity corresponding to the RB,configuration information of at least one RLC entity corresponding tothe RB, MAC configuration information corresponding to each RLC entitycorresponding to the RB, logic channel configuration message, physicallayer configuration information, an identifier of a service, splitindication information and configuration information of a radio resourcecorresponding to the RB.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, or the twelfth possibleimplementation manner of the ninth aspect, in a thirteenth possibleimplementation manner, the configuration information of the radioresource corresponding to the RB includes at least one of followings: aphysical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, or the thirteenth possibleimplementation manner of the ninth aspect, in a fourteenth possibleimplementation manner, the transmitter is configured to realize thesending the handover request acknowledge message to the source basestation or the core network node in a following manner:

sending the handover request acknowledge message to the source basestation to trigger the source base station to send a handover commandmessage to the user equipment, so as to enable the user equipment toestablish connection with the first target base station and the secondtarget base station; or

sending the handover request acknowledge message to the core networknode to trigger the core network node to send the handover requestacknowledge message to the source base station, thereby triggering thesource base station to send the handover command message to the userequipment, so as to enable the user equipment to establish connectionswith the first target base station and the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, or the fourteenth possibleimplementation manner of the ninth aspect, in a fifteenth possibleimplementation manner, the receiver is further configured to receive aradio resource control RRC connection reconfiguration completion messagesent by the user equipment;

the first target base station further comprises: a processor, whereinthe processor is configured to establish a connection between the firsttarget base station and the user equipment after the first target basestation receives the radio resource control RRC connectionreconfiguration completion message sent by the user equipment.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, or the fifteenth possibleimplementation manner of the ninth aspect, in a sixteenth possibleimplementation manner, the transmitter is further configured to send,after the first target base station receives the RRC connectionreconfiguration completion message sent by the user equipment, ahandover indication message of the user equipment to the second targetbase station, for indicating that the second target base station tostarts use a resource configured to the user equipment.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, the fifteenth possibleimplementation manner of the ninth aspect, or the sixteenth possibleimplementation manner of the ninth aspect, in a seventeenth possibleimplementation manner, the receiver is further configured to receive,after the first target base station sends the handover indicationmessage of the user equipment to the second target base station, ahandover indication reply message of the user equipment sent by thesecond target base station, wherein the handover indication replymessage of the user equipment comprises: third type of GTP tunnelendpoint information corresponding to an identifier of an RAB acceptedby the second target base station, wherein the third type of GTP tunnelendpoint information is used for requesting the core network node toswitch a GTP tunnel endpoint.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, the fifteenth possibleimplementation manner of the ninth aspect, the sixteenth possibleimplementation manner of the ninth aspect, or the seventeenth possibleimplementation manner of the ninth aspect, in an eighteenth possibleimplementation manner, the transmitter is further configured to send,after the first target base station receives the RRC connectionreconfiguration completion message sent by the user equipment, a pathswitch request message to the core network node to request to hand overa service corresponding to the user equipment in the core network nodeto the first target base station and/or the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, the fifteenth possibleimplementation manner of the ninth aspect, the sixteenth possibleimplementation manner of the ninth aspect, the seventeenth possibleimplementation manner of the ninth aspect, or the eighteenth possibleimplementation manner of the ninth aspect, in a nineteenth possibleimplementation manner, the transmitter is configured to realize thesending the handover request acknowledge message to the source basestation or the core network node in a following manner: sending thehandover request acknowledge message to the source base station or thecore network node to trigger the source base station to send data and/orsignaling of the user equipment in the source base station to the firsttarget base station and/or the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, the fifteenth possibleimplementation manner of the ninth aspect, the sixteenth possibleimplementation manner of the ninth aspect, the seventeenth possibleimplementation manner of the ninth aspect, the eighteenth possibleimplementation manner of the ninth aspect, or the nineteenth possibleimplementation manner of the ninth aspect, in a twentieth possibleimplementation manner, the receiver is further configured to receive thedata and/or signaling of the user equipment sent by the source basestation; and the transmitter is further configured to send correspondingpart of the second target base station in the data and/or signaling ofthe user equipment to the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, the fifteenth possibleimplementation manner of the ninth aspect, the sixteenth possibleimplementation manner of the ninth aspect, the seventeenth possibleimplementation manner of the ninth aspect, the eighteenth possibleimplementation manner of the ninth aspect, the nineteenth possibleimplementation manner of the ninth aspect, or the twentieth possibleimplementation manner, in a twenty-first possible implementation manner,the triggering the source base station to send the data and/or signalingof the user equipment in the source base station to the first targetbase station and/or the second target base station, includes: triggeringthe source base station to send corresponding part of the first targetbase station in the data and/or signaling of the user equipment to thefirst target base station, and to send corresponding part of the secondtarget base station in the data and/or signaling of the user equipmentto the second target base station.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, the fifteenth possibleimplementation manner of the ninth aspect, the sixteenth possibleimplementation manner of the ninth aspect, the seventeenth possibleimplementation manner of the ninth aspect, the eighteenth possibleimplementation manner of the ninth aspect, the nineteenth possibleimplementation manner of the ninth aspect, the twentieth possibleimplementation manner, or the twenty-first possible implementationmanner, in a twenty-second possible implementation manner, the dataand/or signaling of the user equipment comprise(s) at least one offollowings: data of a service corresponding to the user equipment, whichhas been sent without receiving a reply ACK, data of the servicecorresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN state transfer information and an end marker packet.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, the fifteenth possibleimplementation manner of the ninth aspect, the sixteenth possibleimplementation manner of the ninth aspect, the seventeenth possibleimplementation manner of the ninth aspect, the eighteenth possibleimplementation manner of the ninth aspect, the nineteenth possibleimplementation manner of the ninth aspect, the twentieth possibleimplementation manner, the twenty-first possible implementation manner,or the twenty-second possible implementation manner, in a twenty-thirdpossible implementation manner, the end marker packet is used fortriggering the first target base station and/or the second target basestation to receive data sent by a serving gateway in sequence.

In combination with the ninth aspect, the first possible implementationmanner of the ninth aspect, the second possible implementation manner ofthe ninth aspect, the third possible implementation manner of the ninthaspect, the fourth possible implementation manner of the ninth aspect,the fifth possible implementation manner of the ninth aspect, the sixthpossible implementation manner of the ninth aspect, the seventh possibleimplementation manner of the ninth aspect, the eighth possibleimplementation manner of the ninth aspect, the ninth possibleimplementation manner of the ninth aspect, the tenth possibleimplementation manner of the ninth aspect, the eleventh possibleimplementation manner of the ninth aspect, the twelfth possibleimplementation manner of the ninth aspect, the thirteenth possibleimplementation manner of the ninth aspect, the fourteenth possibleimplementation manner of the ninth aspect, the fifteenth possibleimplementation manner of the ninth aspect, the sixteenth possibleimplementation manner of the ninth aspect, the seventeenth possibleimplementation manner of the ninth aspect, the eighteenth possibleimplementation manner of the ninth aspect, the nineteenth possibleimplementation manner of the ninth aspect, the twentieth possibleimplementation manner, the twenty-first possible implementation manner,the twenty-second possible implementation manner, or the twenty-thirdpossible implementation manner, in a twenty-fourth possibleimplementation manner, the receiver is configured to realize thereceiving the handover request message sent by the source base stationin a following manner: receiving the handover request message, whichcomes from the source base station, forwarded by the core network node.

In a tenth aspect, a base station is provided, the base station is afirst source base station, the source base station includes: atransmitter, configured to send a handover request message to a targetbase station, to make a request for a handover of a user equipment fromthe first source base station and a second source base station to thetarget base station; and a receiver, configured to receive a handoverrequest acknowledge message sent by the target base station, wherein thetransmitter is further configured to send a handover command message tothe user equipment, and notify the user equipment to hand over from thefirst source base station and the second source base station to thetarget base station.

In a first possible implementation manner of the tenth aspect, thetransmitter is further configured to send, before the first source basestation sends the handover request message to the target base station, ahandover initiation request message to the second source base station,to make a request for a handover of the user equipment from the secondsource base station to the target base station; and the receiver isfurther configured to receive a handover initiation response messagefrom the second source base station, and generating the handover requestmessage according to the handover initiation response message.

In combination with the tenth aspect, or the first possibleimplementation manner of the tenth aspect, in a second possibleimplementation manner, the transmitter is further configured to send,before the first source base station sends the handover request messageto the target base station, a handover initiation request message to thesecond source base station through a local gateway; and the receiver isfurther configured to receive the handover request message from thelocal gateway, wherein the handover request message is generated by thelocal gateway according to a handover initiation response message fromthe second source base station.

In combination with the tenth aspect, the first possible implementationmanner of the tenth aspect, or the second possible implementation mannerof the tenth aspect, in a third possible implementation manner, thetransmitter is further configured to send, after the first source basestation receives the handover request acknowledge message sent by thetarget base station, a handover execution notification message to thesecond source base station, for notifying the second source base stationto start executing a handover operation.

In combination with the tenth aspect, the first possible implementationmanner of the tenth aspect, the second possible implementation manner ofthe tenth aspect, or the third possible implementation manner of thetenth aspect, in a fourth possible implementation manner, the receiveris further configured to receive a handover execution notificationresponse message sent by the second source base station, wherein thehandover execution notification response message comprises: SN statustransfer information corresponding to at least one RAB served by thesecond source base station, and/or a data packet, in need of forwarding,corresponding to at least one RAB served by the second source basestation.

In combination with the tenth aspect, the first possible implementationmanner of the tenth aspect, the second possible implementation manner ofthe tenth aspect, the third possible implementation manner of the tenthaspect, or the fourth possible implementation manner of the tenthaspect, in a fifth possible implementation manner, the receiver isfurther configured to receive the handover request acknowledge messagesent by the target base station for triggering the first source basestation and/or the second source base station to send data and/orsignaling of the user equipment to the target base station.

In combination with the tenth aspect, the first possible implementationmanner of the tenth aspect, the second possible implementation manner ofthe tenth aspect, the third possible implementation manner of the tenthaspect, the fourth possible implementation manner of the tenth aspect,or the fifth possible implementation manner of the tenth aspect, in asixth possible implementation manner, the triggering the first sourcebase station and/or the second source base station to send the dataand/or signaling of the user equipment to the target base stationcomprises:

triggering the first source base station to send data and/or signalingof the user equipment in the first target base station and the secondtarget base station to the target base station; or

triggering the first source base station to send the data and/orsignaling of the user equipment in the first source base station to thetarget base station, and triggering the second source base station tosend the data and/or signaling of the user equipment in the secondsource base station to the target base station.

In combination with the tenth aspect, the first possible implementationmanner of the tenth aspect, the second possible implementation manner ofthe tenth aspect, the third possible implementation manner of the tenthaspect, the fourth possible implementation manner of the tenth aspect,the fifth possible implementation manner of the tenth aspect, or thesixth possible implementation manner of the tenth aspect, in a seventhpossible implementation manner, the data and/or signaling of the userequipment comprises at least one of followings: data of a servicecorresponding to the user equipment which has been sent withoutreceiving a reply ACK, data of the service corresponding to the userequipment with a NACK received, SDU data, serial number SN statustransfer information and an end marker packet.

In combination with the tenth aspect, the first possible implementationmanner of the tenth aspect, the second possible implementation manner ofthe tenth aspect, the third possible implementation manner of the tenthaspect, the fourth possible implementation manner of the tenth aspect,the fifth possible implementation manner of the tenth aspect, the sixthpossible implementation manner of the tenth aspect, or the seventhpossible implementation manner of the tenth aspect, in an eighthpossible implementation manner, the receiver is further configured toreceive, before the first source base station sends the end markerpacket to the target base station, the end marker packet sent by anS-GW.

In combination with the tenth aspect, the first possible implementationmanner of the tenth aspect, the second possible implementation manner ofthe tenth aspect, the third possible implementation manner of the tenthaspect, the fourth possible implementation manner of the tenth aspect,the fifth possible implementation manner of the tenth aspect, the sixthpossible implementation manner of the tenth aspect, the seventh possibleimplementation manner of the tenth aspect, or the eighth possibleimplementation manner of the tenth aspect, in a ninth possibleimplementation manner, the transmitter is further configured to send thehandover request message to the target base station through a localgateway.

In an eleventh aspect, a base station is provided, the base station is asource base station, the source base station includes: a transmitter,configured to send a handover request message to a first target basestation; a receiver, configured to receive a handover requestacknowledge message sent by the first target base station, wherein thehandover request acknowledge message is used for notifying the sourcebase station to hand over the user equipment to at least one target cellof the first target base station and/or at least one target cell of asecond target base station, wherein the transmitter is furtherconfigured to send a handover command message to the user equipment, andindicate the user equipment to hand over to the first target basestation and the second target base station.

In a first possible implementation manner of the eleventh aspect, thehandover request message includes at least one of followings:information of at least one target cell of the second target basestation, measurement report information of the user equipment, contextinformation of the user equipment and information of a service of theuser equipment, wherein the information of the service includes RABinformation of the service.

In combination with the eleventh aspect, or the first possibleimplementation manner of the eleventh aspect, in a second possibleimplementation manner, the information of the service further includesat least one of following:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, or the second possibleimplementation manner of the eleventh aspect, in a third possibleimplementation manner, the GTP tunnel endpoint information is first typeof GTP tunnel endpoint information or fourth type of GTP tunnel endpointinformation, wherein the first type of GTP tunnel endpoint informationis used for establishing a transmission bearer of an S1 interfacebetween a serving gateway S-GW and the first target base station and/orthe second target base station, and the fourth type of GTP tunnelendpoint information is used for establishing a transmission bearer forforwarding data between the first target base station and the secondtarget base station.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, or the third possibleimplementation manner of the eleventh aspect, in a fourth possibleimplementation manner, the handover request reply message includes atleast one of the following items:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation between of atleast one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, or the fourth possibleimplementation manner of the eleventh aspect, in a fifth possibleimplementation manner, the first transparent container configurationincludes at least one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, or the fifth possibleimplementation manner of the eleventh aspect, in a sixth possibleimplementation manner, the configuration information of the RB includesat least one of followings:

configuration information of a PDCP entity corresponding to the RB,configuration information of at least one RLC entity corresponding tothe RB, MAC configuration information corresponding to each RLC entitycorresponding to the RB, logic channel configuration message, physicallayer configuration information, an identifier of a service, splitindication information and configuration information of a radio resourcecorresponding to the RB.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, the fifth possibleimplementation manner of the eleventh aspect, or the sixth possibleimplementation manner of the eleventh aspect, in a seventh possibleimplementation manner, the configuration information of the radioresource of the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time slotinformation, time domain information, code domain information and spacedomain information.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, the fifth possibleimplementation manner of the eleventh aspect, the sixth possibleimplementation manner of the eleventh aspect, or the seventh possibleimplementation manner of the eleventh aspect, in an eighth possibleimplementation manner, the receiver is configured to realize thereceiving the handover request acknowledge message sent by the firsttarget base station in a following manner: receiving the handoverrequest acknowledge message from the first target base station, which isforwarded by a core network element.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, the fifth possibleimplementation manner of the eleventh aspect, the sixth possibleimplementation manner of the eleventh aspect, the seventh possibleimplementation manner of the eleventh aspect, or the eighth possibleimplementation manner of the eleventh aspect, in a ninth possibleimplementation manner, wherein the transmitter is configured to send,after the source base station receives the handover request acknowledgemessage sent by the first target base station, data and/or signaling ofthe user equipment to the first target base station and/or the secondtarget base station.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, the fifth possibleimplementation manner of the eleventh aspect, the sixth possibleimplementation manner of the eleventh aspect, the seventh possibleimplementation manner of the eleventh aspect, the eighth possibleimplementation manner of the eleventh aspect, or the ninth possibleimplementation manner of the eleventh aspect, in a tenth possibleimplementation manner, the transmitter is configured to send, after thesource base station sends the handover command message to the userequipment, data and/or signaling of the user equipment to the firsttarget base station and/or the second target base station.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, the fifth possibleimplementation manner of the eleventh aspect, the sixth possibleimplementation manner of the eleventh aspect, the seventh possibleimplementation manner of the eleventh aspect, the eighth possibleimplementation manner of the eleventh aspect, the ninth possibleimplementation manner of the eleventh aspect, or the tenth possibleimplementation manner of the eleventh aspect, in an eleventh possibleimplementation manner, the transmitter is configured to realize thesending the data and/or signaling of the user equipment to the firsttarget base station and/or the second target base station in a followingmanner:

sending the data and/or signaling of the user equipment to the firsttarget base station, for enabling the first target base station to sendcorresponding part of the second target base station in the data and/orsignaling of the user equipment to the second target base station; or

sending corresponding part of the first target base station in the dataand/or signaling of the user equipment to the first target base station,and sending corresponding part of the second target base station in thedata and/or signaling of the user equipment to the second target basestation.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, the fifth possibleimplementation manner of the eleventh aspect, the sixth possibleimplementation manner of the eleventh aspect, the seventh possibleimplementation manner of the eleventh aspect, the eighth possibleimplementation manner of the eleventh aspect, the ninth possibleimplementation manner of the eleventh aspect, the tenth possibleimplementation manner of the eleventh aspect, or the eleventh possibleimplementation manner of the eleventh aspect, in a twelfth possibleimplementation manner, the data and/or signaling of the user equipmentcomprise(s) at least one of followings: data of a service correspondingto the user equipment, which has been sent without receiving a replyACK, data of the service corresponding to the user equipment, of which aresponse of non-acknowledgement NACK is received, data of service dataunit SDU, serial number SN status transfer information and an end markerpacket.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, the fifth possibleimplementation manner of the eleventh aspect, the sixth possibleimplementation manner of the eleventh aspect, the seventh possibleimplementation manner of the eleventh aspect, the eighth possibleimplementation manner of the eleventh aspect, the ninth possibleimplementation manner of the eleventh aspect, the tenth possibleimplementation manner of the eleventh aspect, the eleventh possibleimplementation manner of the eleventh aspect, or the twelfth possibleimplementation manner of the eleventh aspect, in a thirteenth possibleimplementation manner, the end marker packet is used for triggering thefirst target base station and/or the second target base station toreceive data sent by a serving gateway in sequence.

In combination with the eleventh aspect, the first possibleimplementation manner of the eleventh aspect, the second possibleimplementation manner of the eleventh aspect, the third possibleimplementation manner of the eleventh aspect, the fourth possibleimplementation manner of the eleventh aspect, the fifth possibleimplementation manner of the eleventh aspect, the sixth possibleimplementation manner of the eleventh aspect, the seventh possibleimplementation manner of the eleventh aspect, the eighth possibleimplementation manner of the eleventh aspect, the ninth possibleimplementation manner of the eleventh aspect, the tenth possibleimplementation manner of the eleventh aspect, the eleventh possibleimplementation manner of the eleventh aspect, the twelfth possibleimplementation manner of the eleventh aspect, or the thirteenth possibleimplementation manner of the eleventh aspect, in a fourteenth possibleimplementation manner, the transmitter is configured to realize thesending the handover request message to the first target base station ina following manner: sending the handover request message to the firsttarget base station through a core network node.

In a twelfth aspect, a base station is provided, the base station is atarget base station, the target base station includes: a receiver,configured to receive a handover request message sent by a first sourcebase station, wherein the handover request message is used for making arequest for a handover of a user equipment from the first source basestation and a second source base station to the target base station; anda transmitter, configured to send a handover request acknowledge messageto the first source base station, wherein the handover requestacknowledge message is used for indicating that the handover of the userequipment from the first source base station and the second source basestation to the target base station is accepted.

In a first possible implementation manner of the twelfth aspect, thetransmitter is further configured to receive, after the target basestation sends the handover request acknowledge message to the firstsource base station, data and/or signaling of the user equipment sent bythe first source base station and/or the second source base station.

In combination with the twelfth aspect, or the first possibleimplementation manner of the twelfth aspect, in a second possibleimplementation manner, the receiver is configured to realize that thetarget base station to receives the data and/or signaling of the userequipment sent by the first source base station and/or the second sourcebase station in a following manner:

receiving the data and/or signaling of the user equipment sent by thefirst source base station, and/or receiving the data and/or signaling ofthe user equipment sent by the second source base station; or

receiving the data and/or signaling of the user equipment correspondingto the first source base station and/or the second source base station,sent by the first source base station.

In combination with the twelfth aspect, the first possibleimplementation manner of the twelfth aspect, or the second possibleimplementation manner of the twelfth aspect, in a third possibleimplementation manner, the data and/or signaling of the user equipmentcomprise(s) at least one of followings: data of a service correspondingto the user equipment which has been sent without receiving a reply ACK,data of a service corresponding to the user equipment with a NACKreceived, SDU data, serial number SN status transfer information and anend marker packet.

In combination with the twelfth aspect, the first possibleimplementation manner of the twelfth aspect, the second possibleimplementation manner of the twelfth aspect, or the third possibleimplementation manner of the twelfth aspect, in a fourth possibleimplementation manner, the receiver is configured to realize thereceiving the handover request message sent by the first source basestation in a following manner: receiving the handover request message,which comes from the first source base station, forwarded by a localgateway.

In combination with the twelfth aspect, the first possibleimplementation manner of the twelfth aspect, the second possibleimplementation manner of the twelfth aspect, the third possibleimplementation manner of the twelfth aspect, or the fourth possibleimplementation manner of the twelfth aspect, in a fifth possibleimplementation manner, after the target base station sends the handoverrequest reply message to the first source base station, the receiver isfurther configured to receive, after the target base station sends thehandover request acknowledge message to the first source base station, aradio resource control RRC connection reconfiguration completion messagesent by the user equipment, and control the target base station toestablish connection with the user equipment.

By means of an above-mentioned solution, after receiving a handoverrequest message, a first target base station notifies a second targetbase station to hand over a user equipment thereon, and sends a handoverrequest acknowledge message to the source base station, for notifyingthe source base station of handing over the user equipment to the firsttarget base station and the second target base station, so that thehandover can be achieved when there exists a target cell.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a flowchart of a handover processing method according toembodiment 1 of the present invention;

FIG. 2 is a flowchart of a handover processing method according toembodiment 2 of the present invention;

FIG. 3 is a schematic diagram of a handover processing method accordingto embodiment 3 of the present invention;

FIG. 4 is a schematic diagram of a handover processing method accordingto embodiment 4 of the present invention;

FIG. 5 is a flowchart of a handover processing method according toembodiment 5 of the present invention;

FIG. 6 is a flowchart of a handover processing method according toembodiment 6 of the present invention;

FIG. 7 is a schematic diagram of a handover processing method accordingto embodiment 7 of the present invention;

FIG. 8 is a schematic diagram of a handover processing method accordingto embodiment 8 of the present invention;

FIG. 9 is a schematic diagram of a handover processing method accordingto embodiment 9 of the present invention;

FIG. 10 is a block diagram of a structure of a base station according toembodiment 10 of the present invention;

FIG. 11 is a block diagram of a structure of a base station according toembodiment 11 of the present invention;

FIG. 12 is a block diagram of a structure of a base station according toembodiment 12 of the present invention;

FIG. 13 is a block diagram of a structure of a base station according toembodiment 13 of the present invention;

FIG. 14 is a block diagram of a structure of a base station according toembodiment 14 of the present invention;

FIG. 15 is a block diagram of a specific structure of a base stationaccording to embodiment 14 of the present invention;

FIG. 16 is a block diagram of a structure of a base station according toembodiment 15 of the present invention;

FIG. 17 is a block diagram of a structure of a base station according toembodiment 16 of the present invention; and

FIG. 18 is a block diagram of a structure of a base station according toembodiment 17 of the present invention.

DESCRIPTION OF EMBODIMENTS

A clear and complete description of technical solutions in theembodiments of the present invention will be given below, in combinationwith the accompanying drawings in the embodiments of the presentinvention. Apparently, the embodiments described below are merely apart, but not all, of the embodiments of the present invention. All ofother embodiments, obtained by those of ordinary skills in the art basedon the embodiments of the present invention without any creative effort,fall into the protection scope of the present invention.

A network node (for example, a base station) in this application, whichis not limited herein, may be a base station provided with an integralresource management module. It may also a baseband processing module anda radio frequency unit, a remote radio head (RRH), a radio remote unit(RRU) and an antenna. It may also be a relay.

Embodiment 1

The embodiment provides a handover processing method. The method may beapplied to a handover without a loss of data under a multi-cell splitscenario, for example, it is used for a handover of a UE from a sourcebase station to multiple target base stations.

FIG. 1 is a flowchart of a handover processing method according toembodiment 1 of the present invention. As shown in FIG. 1, the methodincludes:

step 101, receiving, by a first target base station, a handover requestmessage sent by a source base station;

step 102, sending, by the first target base station, a first messageaccording to the handover request message, to a second target basestation to notify the second target base station that a handover of partor all of a service of a user equipment to the second target basestation is to be performed; and

step 103, sending, by the first target base station, a handover requestacknowledge message to the source base station or a core network node,wherein the handover request acknowledge message is used for notifyingthe source base station or the core network node to hand over the userequipment to at least one target cell of the first target base stationand/or at least one target cell of the second target base station.

In the solution, the first target base station determines, according tothe handover request message, that the UE may also be handed over to thesecond target base station, notifies the second target base station, andfeeds back the handover request acknowledge message to the source basestation, for enabling the source base station to hand over the userequipment to the first target base station and the second target basestation, so that the handover of the UE from one source base station tomultiple target base stations is enabled, a normal handover operationwithout a loss of data under a multi-cell split scenario is achieved,and the supporting problem that the handover without the loss of dataunder the multi-cell split scenario could not be supported in the priorart that is solved.

Preferably, the user equipment hands over all services to the secondtarget base station, and the first target base station provides asignaling service for the user equipment.

Preferably, the sending, by the first target base station, a firstmessage, according to the handover request message, to a second targetbase station, may include following implementation manners.

First manner: the first target base station determines, according to ameasurement report of the user equipment and/or radio access bear RABinformation of the user equipment in the handover request message, thatthe handover of the part or all of the service of the user equipment tothe second target base station. Then the first target base station sendsthe first message to the second target base station to notify the secondtarget base station of the handover to be implemented.

Second manner: the source base station determines, according toinformation of a target cell of the second target base station in thehandover request message, that the handover of the part or all of theservice of the user equipment to the second target base station. Thesource base station carries information of the second target basestation in the handover request message. Then the first target basestation sends, according to the information of the second target basestation in the handover request message, the first message to the secondtarget base station.

In the embodiment of the present invention, after the user equipment ishanded over to the first target base station and the second target basestation, the first target base station and the second target basestation may simultaneously provide a data service for the userequipment, or the first target base station provides a signaling servicefor the user equipment, and the second target base station provides adata service for the user equipment.

Preferably, the handover request message includes at least one offollowings: information of at least one target cell of the second targetbase station, measurement report information of the user equipment,context information of the user equipment and information of a serviceof the user equipment, wherein the information of the service includesRAB information of the service.

The first message may include information of at least one service of theuser equipment, wherein the information of the service includes RABinformation of the service and/or configuration information of a radiobear RB.

The information of the service further includes at least one offollowings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet, wherein the frequencydomain information may include but not limited to position informationof a physical resource block, the space domain information may includebut not limited to wave beam information, flow information and spatialencoding matrix information, and the code domain information may includebut not limited to an address code, a scrambling code and a sequenceinitializing code, wherein the GTP tunnel endpoint information mayinclude a transport layer address and a GTP TEID.

Preferably, the GTP tunnel endpoint information is first type of GTPtunnel endpoint information or fourth type of GTP tunnel endpointinformation, wherein the first type of GTP tunnel endpoint informationis used for establishing a transmission bearer of an S1 interfacebetween a serving gateway S-GW and the first target base station and/orthe second target base station, and the fourth type of GTP tunnelendpoint information is used for establishing a transmission bearer forforwarding data between the first target base station and the secondtarget base station.

Preferably, the configuration information of the RB includes:

a packet data convergence protocol PDCP layer, a radio link control RLClayer, a medium access control MAC layer and configuration informationof a physical layer; or configuration information of an RLC layer, anMAC layer and a physical layer.

In an implementation manner of the embodiment of the present invention,after the first target base station sends the first message to thesecond target base station, the method further includes:

the first target base station receives a second message sent by thesecond target base station, for indicating information regarding whetherthe handover of the part or all of the service of the user equipment tothe second target base station is accepted by the second target basestation. In the embodiment, the second target base station will feedback information regarding whether the handover is accepted, thereby thehandover is performed more effectively. It should be noted that, thestep is an optional step, and the first target base station may alsocommand the second target base station to perform the handover directly,without obtaining an agreement of the second target base station.

Preferably, the second message includes at least one of followings:

an identifier of the user equipment, first information and indicationinformation,

wherein the indication information includes at least one of followings:indication information of refusing the handover of the part or all ofthe service of the user equipment to the second target base station,indication information of accepting the handover of the part or all ofthe service of the user equipment to the second target base station, andindication information of modifying the first message.

The first information includes at least one of followings: an identifierof an RB accepted by the second target base station, configurationinformation of an RB accepted by the second target base station, anidentifier of an RAB corresponding to an RB accepted by the secondtarget base station, an identifier of an RB whose resource configurationis rejected by the second target base station, and an identifier of anRAB corresponding to an RB whose resource configuration is rejected bythe second target base station.

The second message may further include at least one of followings:

fourth type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station;

second type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe second type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between thesecond target base station and the source base station; and

third type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe third type of GTP tunnel endpoint information is used for requestinga core network node to convert a GTP tunnel endpoint.

Preferably, the handover request acknowledge message includes at leastone of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation between atleast one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

Preferably, the first transparent container configuration includes atleast one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

The configuration information of the RB includes at least one offollowings:

configuration information of a PDCP entity corresponding to the RB,configuration information of at least one RLC entity corresponding tothe RB, MAC configuration information corresponding to each RLC entitycorresponding to the RB, logic channel configuration message, physicallayer configuration information, an identifier of a service, splitindication information and configuration information of a radio resourcecorresponding to the RB.

Preferably, the configuration information of the radio resourcecorresponding to the RB includes at least one of followings:

a physical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information.

The first message may include an identifier of the user equipment andinformation of part or all of a service. After receiving the firstmessage, the second target base station may know that the part or all ofthe service of the user equipment will be handed over to the secondtarget base station, wherein the frequency domain information mayinclude but not limited to position information of a physical resourceblock, the space domain information may include but not limited to wavebeam information, flow information and spatial encoding matrixinformation, and the code domain information may include but not limitedto an address code, a scrambling code and a sequence initializing code.

Preferably, the first target base station determine whether the secondtarget base station accepts the handover of the part or all of theservice of the user equipment to the second target base station may berealized in one of following manners.

The first target base station determines, according to the first messageand the identifier of the user equipment in the second message, whetherthe second target base station accepts the handover of the part or allof the service of the user equipment to the second target base station,wherein the first information includes at least one of followings: anidentifier of an RB accepted by the second target base station,configuration information of an RB accepted by the second target basestation, an identifier of an RAB corresponding to an RB accepted by thesecond target base station, an identifier of an RB whose resourceconfiguration is rejected of the second target base station, and anidentifier of an RAB corresponding to an RB whose resource configurationis rejected by the second target base station.

The first target base station determines, according to the indicationinformation, the first information and the identifier of the userequipment in the second message, whether the second target base stationaccepts the handover of the part or all of the service of the userequipment to the second target base station, wherein the firstinformation includes at least one of followings: an identifier of an RBaccepted by the second target base station, configuration information ofan RB accepted by the second target base station, an identifier of anRAB corresponding to an RB accepted by the second target base station,an identifier of an RB whose resource configuration is rejected by thesecond target base station, and an identifier of an RAB corresponding toan RB whose resource configuration is rejected by the second target basestation. The indication information includes at least one of followings:indication information of information refusing the handover of the partof or all of the service of the user equipment to the second target basestation, indication information of accepting the handover of the part orall of the service of the user equipment to the second target basestation, and indication information of modifying the first message.

The information of the service accepted by the second target basestation may include at least one of followings: an identifier of an RBaccepted by the second target base station, configuration information ofan RB accepted by the second target base station, an identifier of anRAB corresponding to an RB accepted by the second target base station,an identifier of the RB whose resource configuration is rejected by thesecond target base station, and an identifier of an RAB corresponding toan RB whose resource configuration is rejected by the second target basestation.

Preferably, the handover request acknowledge message may trigger thesource base station or the core network node to send the handovercommand message to the user equipment, and then, the user equipmentestablishes connections with the first target base station and thesecond target base station.

After sending the handover command message, the user equipment sendsinformation to the first target base station and the second target basestation, and the information includes an unordered packet dataconvergence protocol service data unit PDCP SDU in a reordering bufferregion in a PDCP entity in a protocol stack of the user equipmentcorresponding to the source base station.

In another preferable implementation manner of the embodiment of thepresent invention, after the first target base station sends thehandover request acknowledge message to the source base station or thecore network node, the first target base station receives a radioresource control RRC connection reconfiguration completion message sentby the user equipment, and establishes a connection with the userequipment (for example, establishing a signaling connection).

Preferably, after the first target base station receives the radioresource control RRC connection reconfiguration completion message sentby the user equipment, the first target base station sends a handoverindication message of the user equipment to the second target basestation, and the message may indicate that the second target basestation to establish a data connection with the user equipment and anS-GW. The message may be a command message for instructing the secondtarget base station to establish a data connection with the userequipment and the S-GW, and it may also be a request message forrequesting the second target base station to establish a data connectionwith the user equipment and the S-GW. When the handover indicationmessage is a request message, the first target base station may alsoreceive a handover indication reply message of the user equipment sentby the second target base station, and establish a transmission bearerbetween the second target base station and the serving gateway S-GWaccording to first general packet radio service tunneling protocol GTPtunnel endpoint information of the second target base station, in orderto establish the data connection between the second target base stationand the S-GW.

After the first target base station sends the handover indicationmessage of the user equipment to the second target base station, thefirst target base station sends a path switch request message to thecore network node to request to hand over a service corresponding to theuser equipment in the core network node to the first target base stationand/or the second target base station. After receiving the path switchrequest message, the core network node may terminate the communicationwith the source base station, and establish a communication with thefirst target base station and/or the second target base station.

Preferably, the first target base station sending the handover requestacknowledge message to the source base station or the core network nodemay trigger the source base station to send data and/or signaling of thelocal user equipment to the first target base station and the secondtarget base station. Before the handedover to the first target basestation and the second target base station, the user equipment hascommunicated with the source base station, and some data of the userequipment has already existed in the source base station. after thehandedover to the first target base station and/or the second targetbase station, the user equipment may not send received data, which isacknowledged by the source base station, to the target base station,resulting in data loss in the target base station. In the embodiment,the source base station sends the data of the user equipment therein tothe first target base station and/or the second target base station,thereby achieving a handover without a loss of data.

Before triggering the source base station to send the data and/orsignaling of the user equipment in the source base station to the firsttarget base station and the second target base station, a correspondingtransmission bearer may be established, and the establishment manner mayinclude:

the first target base station receiving third GTP tunnel endpointinformation sent by the second target base station, and establishes atransmission bearer from the first target base station to the secondtarget base station according to the third GTP tunnel endpointinformation; and

the first target base station sending fourth GTP tunnel endpointinformation and fifth GTP tunnel endpoint information to the source basestation, wherein the fourth GTP tunnel endpoint information is used bythe source base station for establishing a transmission bearer from thesource base station to the first target base station, and the fifth GTPtunnel endpoint information is used for the source base stationestablishing a transmission bearer from the source base station to thefirst target base station for relaying data of the second target basestation.

Preferably, the first target base station receives the data and/orsignaling of the user equipment sent by the source base station, andsends corresponding part of the second target base station in the dataand/or signaling of the user equipment to the second target basestation.

Preferably, before triggering the source base station to send the dataand/or signaling of the user equipment in the source base station to thefirst target base station and the second target base station, the methodfurther includes:

receiving, by the first target base station, sixth GTP tunnel endpointinformation sent by the second target base station; and

sending, by the first target base station, the sixth GTP tunnel endpointinformation and seventh tunnel endpoint information to the source basestation, wherein the sixth GTP tunnel endpoint information is used forthe source base station establishing a transmission bearer from thesource base station to the second target base station, and the seventhGTP tunnel endpoint information is used for the source base stationestablishing a transmission bearer from the source base station to thefirst target base station.

Preferably, the triggering the source base station to send the dataand/or signaling of the user equipment in the source base station to thefirst target base station and the second target base station, mayinclude: triggering the source base station to send corresponding partof the first target base station in the data and/or signaling of theuser equipment to the first target base station, and send correspondingpart to the second target base station in the data and/or signaling ofthe user equipment to the second target base station.

Preferably, the data and/or signaling of the user equipment includes atleast one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data of aservice corresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN status transfer information and an end marker packet.

The end marker packet may be used for triggering the first target basestation and/or the second target base station to receive data sent bythe serving gateway in sequence.

Preferably, the receiving, by a first target base station, a handoverrequest message sent by a source base station includes: receiving, bythe first target base station, the handover request message, which comesfrom the source base station, forwarded by the core network node.

The embodiment provides a technology of a handover without a loss ofdata under a multi-cell split scenario and provides a technology of asignaling control and a technology of forwarding without a loss of dataduring a handover, thereby realizing a normal handover operation withouta loss of data under a multi-cell split scenario, and a supportingproblem that basing on that one UE is served by one cell, a handoverflow in the conventional art cannot support a handover without a loss ofdata under the multi-cell split scenario, is solved.

Embodiment 2

FIG. 2 is a flowchart of a handover processing method according to theembodiment 2 of the present invention, as shown in FIG. 2, the methodincludes:

step 201, sending, by a source base station, a handover request messageto a first target base station;

step 202, receiving, by the source base station, a handover requestacknowledge message sent by the first target base station, wherein thehandover request acknowledge message is used for notifying the sourcebase station to hand over the user equipment to at least one target cellof the first target base station and/or at least one target cell of asecond target base station; and

step 203, sending, by the source base station, a handover commandmessage to the user equipment, to indicate the user equipment to handover to the first target base station and the second target basestation.

Preferably, the handover request message may include at least one offollowings: information of at least one target cell of the second targetbase station, measurement report information of the user equipment,context information of the user equipment and information of a serviceof the user equipment, wherein the information of the service includesRAB information of the service.

Wherein, the information of the service may further include at least oneof followings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein, the configuration coordination information of the radioresource of the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

Preferably, the GTP tunnel endpoint information is first type of GTPtunnel endpoint information or fourth type of GTP tunnel endpointinformation, wherein the first type of GTP tunnel endpoint informationis used for establishing a transmission bearer of an S1 interfacebetween a serving gateway S-GW and the first target base station and/orthe second target base station, and the fourth type of GTP tunnelendpoint information is used for establishing a transmission bearer forforwarding data between the first target base station and the secondtarget base station.

Preferably, the handover request acknowledge message includes at leastone of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation between atleast one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

Optionally, the first transparent container configuration includes atleast one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station;

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

Optionally, the configuration information of the RB includes at leastone of followings: configuration information of a PDCP entitycorresponding to the RB, configuration information of at least one RLCentity corresponding to the RB, MAC configuration informationcorresponding to each RLC entity corresponding to the RB, logic channelconfiguration message, physical layer configuration information, anidentifier of a service, split indication information and configurationinformation of a radio resource corresponding to the RB.

Optionally, the configuration information of the radio resource of theRB includes at least one of followings: a physical cell identifier, alogic cell identifier, a virtual cell identifier, frequency information,carrier information, radio resource block information, subcarrierinformation, sub-frame information, time slot information, time domaininformation, code domain information and space domain information.

Preferably, the source base station may receive the handover requestacknowledge message sent by the first target base station, which isforwarded by a core network element.

Preferably, after the source base station receives the handover requestacknowledge message sent by the first target base station, the sourcebase station sends data and/or signaling of the user equipment to thefirst target base station and/or the second target base station.

In a preferable implementation manner of the embodiment, after thesource base station sends the handover command message to the userequipment, the source base station sends data and/or signaling of theuser equipment to the first target base station and/or the second targetbase station.

Preferably, the sending, by the source base station, the data and/orsignaling of the user equipment to the first target base station and/orthe second target base station, includes:

sending, by the source base station, the data and/or signaling of theuser equipment to the first target base station, for enabling the firsttarget base station to send corresponding part of the second target basestation in the data and/or signaling of the user equipment to the secondtarget base station; or

sending, by the source base station, corresponding part of the firsttarget base station in the data and/or signaling of the user equipmentto the first target base station, and sending corresponding part of thesecond target base station in the data and/or signaling of the userequipment to the second target base station.

Preferably, the data and/or signaling of the user equipment includes atleast one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data ofthe service corresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN status transfer information and an end marker packet.

Optionally, the end marker packet is used for triggering the firsttarget base station and/or the second target base station to receivedata sent by a serving gateway in sequence.

In another preferable implementation manner of the embodiment, thesource base station sends the handover request message to the firsttarget base station through a core network node.

The embodiment provides a technology of a handover without a loss ofdata under a multi-cell split scenario and provides a technology of asignaling control and a technology of forwarding without a loss of dataduring a handover, thereby realizing a normal handover operation withouta loss of data under a multi-cell split scenario, and a supportingproblem that basing on that one UE is served by one cell, a handoverflow in the conventional art cannot support a handover without a loss ofdata under the multi-cell split scenario, is solved.

Embodiment 3

The embodiment provides a method for handing over a UE to multi cells.In the embodiment, the UE is handed over from a base station to a targetbase station 1 (a first target base station) providing a cellaggregation service and a target auxiliary base station 2 (a secondtarget base station), wherein there is a connecting interface betweenthe auxiliary target base station 2 and a gateway.

FIG. 3 is a schematic diagram of a handover processing method accordingto embodiment 3 of the present invention, as shown in FIG. 3, the methodshown in the embodiment includes following steps:

Step 301, through a handover decision, the source base stationdetermines to hand over the UE to the first target base station, and abasis of the decision may be a measurement report of the UE. And then,the source base station sends a first handover required message to anMME, and optional parameters carried in the message include: informationof a recommended target cell group (such as information and cellinformation of the first target base station and the second target basestation), a measurement report on cells of the two base stations, radioresource control (RRC) context information of the UE, contextinformation of an S1 interface of the UE and information of a radioaccess bear (RAB), and the like. In the step, the source base stationmay also determine to hand over the UE to the first target base stationand the second target base station simultaneously. At this time, thefirst handover required message may include: information of arecommended target cell group (information and cell information of thefirst target base station and the second target base station), RRCcontext information of the UE, context information of an S1 interface ofthe UE and information of an RAB. Namely, there may be no measurementreport on the cells of the two base stations in the first handoverrequired message. If the source base station, according to themeasurement report of the UE, determines to hand over the UE to thefirst target base station merely, a measurement report of a cell of thesecond target base station may be carried in the first handover requiredmessage, so that the first target base station determines, according tothe measurement report, to hand over the UE to the first target basestation and the second target base station simultaneously. At this time,the first handover required message may include: the information of therecommended target cell group (information and cell information of thefirst target base station), the measurement report on the cells of thetwo base stations, the RRC context information of the UE, the contextinformation of the S1 interface of the UE and the information of theRAB.

In addition, the first handover required message may further include atleast one of followings: an identifier of the user equipment allocatedat the source base station, information of at least one target cell ofthe first target base station, a globally unique MME (MobilityManagement Entity, Globally Unique MME) identifier (ID) (or GUMMEI forshort) and context information of the user equipment, wherein thecontext information of the user equipment includes the combination of atleast one item of followings: an identifier of at least one RAB of theuser equipment, quality of service (QoS) information corresponding to anRAB and the first type of GTP tunnel endpoint information correspondingto an RAB. The first type of GTP tunnel endpoint information is used forestablishing a transmission bearer of an S1 interface between a basestation (the first target base station and/or the second target basestation) and an S-GW.

Step 302, after receiving the first handover required message, the MMEsends a handover request message to the first target base station, andthe optional parameters carried in the message include: a recommendedtarget cell group, namely information and cell information of the firsttarget base station and the second target base station, a measurementreport on the cells of the two base stations, RRC context information ofthe UE, context information of an S1 interface of the UE, E-RABinformation and the like. The parameters carried in the handover requestmessage sent by the MME may be the same as the parameters carried in thehandover request message sent by the source base station.

Step 303, after receiving the handover request message, the first targetbase station sends a first message (the message may be called as aresource status detection message) to the second target base station, inorder to notify the second target base station of information of theabove-mentioned UE (e.g., information of an E-RAB, an RAB) andinformation that the UE is about to be assigned to the second targetbase station.

A manner of determining the second target base station may include atleast one of followings: determining, by the first target base station,according to a recommended target cell group (such as the first targetbase station and the second target base station) sent by the MME,determining, by the first target base station, according to a result ofa measurement report of the UE on cells of the two base stations, anddetermining, by the first target base station, according to conditionsof status of a resource, a load and the like of an auxiliary basestation, known by itself, and RAB information of the UE.

Optionally, the resource status detection message may include radio bearconfiguration information corresponding to an E-RAB information of theUE, for example, if the allocation is performed by the first target basestation actively, the resource status detection message may includefollowing information: an identifier of the UE (for example, a cellradio network temporary identifier (C-RNTI) or an XmAP (Xm is aninterface between the first target base station and the second targetbase station) identifier) and split indication information, wherein thesplit indication information includes data split information based on anRB or data split information based on a packet.

The resource status detection message may further include serviceinformation (for example, information of a service to be handed over tothe second target base station) of at least one service, wherein theservice information includes quality information of a service and/orconfiguration information of an RB, and the resource status detectionmessage instructs the second target base station to perform a resourceconfiguration according to the service information of the at least oneservice.

Optionally, the data split information based on the RB means that thefirst target base station sends SDU data of a packet data convergenceprotocol (PDCP) layer of a service of the UE to the second target basestation. At this time, after receiving the information of at least oneservice, the second target base station may perform correspondingresource configuration for the information of at least one service, toconfigure a PDCP layer, a radio link control (RLC) layer, a mediumaccess control (MAC) layer and a physical layer (Phy) of an RBcorresponding to the information of at least one service. The data splitinformation based on the packet refers to SDU data of an RLC layer of aservice of the UE sent from the first target base station to the secondtarget base station. At this time, after receiving at least one serviceinformation, the second target base station may perform correspondingresource configuration for the at least one service information, toconfigure an RLC layer, an MAC layer and a physical layer of an RBcorresponding to the at least one service information.

Optionally, when the split indication information includes the datasplit information based on the packet, the second target base stationconfigures, according to information of at least one service, an RLClayer, an MAC layer and a physical layer of an RB corresponding to theat least one service, and the first target base station configures aPDCP layer, an RLC layer, an MAC layer and a physical layer of the RB.

Optionally, the configuration information of the RB includes:configuration information of a PDCP layer, an RLC layer, an MAC layerand a physical layer, or configuration information of an RLC layer, anMAC layer and a physical layer. In this way, the second target basestation may configure the PDCP layer, the RLC layer, the MAC layer andthe physical layer, or the RLC layer, the MAC layer and the physicallayer of the RB corresponding to the service information of at least oneservice.

Optionally, the service information may further include at least one offollowings: configuration coordination information of a radio resourceof RB, an identifier of an RB, an identifier of an RAB and splitindication information.

Optionally, the configuration coordination information of the radioresource of the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information,wherein the frequency domain information may include but not limited toposition information of a physical resource block, the space domaininformation may include but not limited to wave beam information, flowinformation and spatial encoding matrix information, and the code domaininformation may include but not limited to an address code, a scramblingcode and a sequence initializing code.

Step 304, the second target base station replies a second message (themessage may be called as a resource status detection response message)to the first target base station, wherein the message may carryinformation indicating whether the second target base station acceptsthe handover request message.

If the second target base station accepts the handover request message,namely, the second target base station accepts the handover of part orall of a service of the UE to the second target base station, theresource status detection response message includes a confirmation or amodification of a configuration content in the resource status detectionmessage. For example, through a resource status detection message, thefirst target base station notifies the second target base station thatthe handover of multiple services of the UE to the second target basestation is to be performed, the second target base station agrees thehandover of part of services in the multiple services to the secondtarget base station, and notified the first target base station, by aresource status detection response message, of handing over the part ofservices in the multiple services, which is agreed by the second targetbase station, to the second target base station.

Optionally, the resource status detection response message may includeradio bear configuration information corresponding to E-RAB informationof the UE, for example, if the allocation is performed by the secondtarget base station actively, the message may include followinginformation:

an identifier of the UE (such as a C-RNTI or an XmAP identifier); and

split indication information, wherein the split indication informationincludes data split information based on an RB or data split informationbased on a packet.

The resource status detection response message may further includeservice information of at least one service, wherein the serviceinformation includes quality information of a service and/orconfiguration information of an RB.

The resource status detection response message may further include atleast one of followings:

first information and indication information, wherein the firstinformation includes one of followings: information on refusing ahandover of part or all of a service of the user equipment to the secondtarget base station, information on accepting the handover of part orall of a service of the user equipment to the second target basestation, or information on modifying the first message, and theindication information includes at least one of followings: anidentifier of an RB accepted by the second target base station,configuration information of an RB accepted by the second target basestation, an identifier of an RAB corresponding to an RB accepted by thesecond target base station, an identifier of an RB whose resourceconfiguration is rejected by the second target base station, and anidentifier of an RAB corresponding to an RB whose resource configurationis rejected by the second target base station.

The resource status detection response message may further include atleast one of followings:

fourth type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station (forexample, the third GTP tunnel endpoint information), wherein the fourthtype of GTP tunnel endpoint information is used for establishing atransmission bearer for forwarding data between the first target basestation and the second target base station;

second type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station (forexample, sixth GTP tunnel endpoint information), wherein the second typeof GTP tunnel endpoint information is used for establishing atransmission bearer for forwarding data between the second target basestation and the source base station;

third type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepting by the second target base station,wherein the third type of GTP tunnel endpoint information is used forrequesting a core network node to convert a GTP tunnel endpoint.

Optionally, the configuration information of the RB includes:configuration information of a PDCP layer, an RLC layer, an MAC layerand a physical layer, or configuration information of an RLC layer, anMAC layer and a physical layer. In this way, the second target basestation may configure the PDCP layer, the RLC layer, the MAC layer andthe physical layer, or the RLC layer, the MAC layer and the physicallayer of an RB corresponding to the service information of at least oneservice.

Optionally, the service information may further include at least one offollowing items: configuration coordination information of a radioresource of an RB, an identifier of an RB, an identifier of an RAB andsplit indication information.

Optionally, the configuration coordination information of the radioresource of the RB includes at least one of following items: a physicalcell identifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information,wherein the frequency domain information may include but not limited toposition information of a physical resource block; the space domaininformation may include but not limited to wave beam information, flowinformation and spatial encoding matrix information; the code domaininformation may include but not limited to an address code, a scramblingcode and a sequence initializing code.

A PDCP entity of the UE is logically corresponding to a PDCP entity ofthe first target base station, a first RLC entity and a second RLCentity of the UE are logically corresponding to RLC entities of thefirst target base station and the second target base stationrespectively, a first MAC entity and a second MAC entity of the UE arelogically corresponding to MAC entities of the first target base stationand the second target base station respectively.

If the second target base station rejects the handover request message,the resource status detection response message includes a refusal to aconfiguration content in the resource status detection message, forexample, the resource status detection response message includesinformation on refusing the handover of the UE to the second target basestation.

Step 305, the first target base station replies a handover requestacknowledge (Handover Request ACK) message to a core network element (anMME is taken as an example below), the message may include at least oneof followings: a UE identifier, E-RAB information, radio bearinformation, uplink and/or downlink GTP tunnel endpoint information ofthe first target base station (including a transport layer address and aGTP TEID), and uplink and/or downlink GTP tunnel endpoint information ofthe second target base station (including a transport layer address anda GTP TEID), wherein the radio bear information includes a content ofthe resource status detection response message in step 304.

The handover request acknowledge message may include at least one offollowings:

an identifier of the UE allocated at the source base station, anidentifier of the UE allocated at the first target base station and/orthe second target base station, a first transparent containerconfiguration, an identifier of at least one RAB rejected by the firsttarget base station and/or the second target base station, an identifierof at least one RAB accepted by the first target base station, fifthtype of GTP tunnel endpoint information corresponding to an identifierof at least one RAB accepted by the first target base station, anidentifier of at least one RAB accepted by the second target basestation, sixth type of GTP tunnel endpoint information corresponding toan identifier of at least one RAB accepted by the second target basestation, second type of GTP tunnel endpoint information corresponding toan identifier of an RAB accepted by the second target base station, anda corresponding relation between at least one RAB accepted by the firsttarget base station and/or the second target base station and the firsttarget base station and/or the second target base station,

wherein the fifth type of GTP tunnel endpoint information (for example,fourth GTP tunnel endpoint information) is used for establishing atransmission bearer for data forwarding between the first target basestation and the source base station; the sixth type of GTP tunnelendpoint information (for example, fifth GTP tunnel endpointinformation) is used for establishing a transmission bearer forforwarding data between the first target base station and the sourcebase station; and the second type of GTP tunnel endpoint information isused for establishing a transmission bearer for data forwarding betweenthe second target base station and the source base station.

Preferably, the first transparent container configuration may include atleast one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station;

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

Preferably, the configuration information of the RB includes at leastone of following: configuration information of a PDCP entitycorresponding to the RB, configuration information of at least one RLCentity corresponding to the RB, MAC configuration informationcorresponding to each RLC entity corresponding to the RB, logic channelconfiguration message, physical layer configuration information, anidentifier of a service, split indication information and configurationinformation of a radio source corresponding to the RB.

The configuration information of the radio source corresponding to theRB includes at least one of following:

a physical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information, wherein the frequency domain information mayinclude but not limited to position information of a physical resourceblock; the space domain information may include but not limited to wavebeam information, flow information and spatial encoding matrixinformation; the code domain information may include but not limited toan address code, a scrambling code and a sequence initializing code.

Step 306, after receiving the Handover Request ACK (HANDOVER REQUESTACKNOWLEDGE) message replied by the first target base station, the MMEsends a handover command message to the source base station, to notifythe source base station of a resource allocation condition of the targetbase station. The handover command message includes: a UE identifier,E-RAB information, radio bear information. An uplink and/or downlink GTPtunnel endpoint of the first target base station includes a transportlayer address and a GTP TEID, and an uplink and/or downlink GTP tunnelendpoint includes a transport layer address and a GTP TEID of the secondtarget base station, wherein the radio bear information includes acontent of the resource status detection response message in step 304.

Step 307, after receiving the handover command message of the MME, thesource base station sends a handover command message (for example,sending in a form of an RRC connection reconfiguration message) to theUE, and the handover command message includes configuration listinformation of the RB and/or information of a cell of the second targetbase station, so as to enable the UE to configure a corresponding RBaccording to the configuration message. The handover command message mayfurther include: information of a target cell group (for example,information and cell information of the first target base station andthe second target base station), configuration information of a servicein the two base stations (the configuration information may be radiobear information and may include a content of the resource statusdetection response message in step 304), security information and thelike. Then, step 310 is implemented.

It should be noted that, as long as the source base station receives theHANDOVER REQUEST ACKNOWLEDGE, or as long as the source base stationstarts to send the handover command to the UE, a forwarding of data fromthe source base station to the target base station begins, so that adata plane transmission as shown in step 308 and step 309 may beperformed. Since in step 307, the source base station begins to send thehandover command to the UE, step 308 and step 309 may be performed afterstep 307, for example, a downlink transmission in step 308, or step 309may be implemented, wherein a sequence of an implementation of step 308and step 309 is not limited.

Step 308, in a downlink direction, the source base station forwards,according to conditions of services undertaken by cells in the firsttarget base station and the second target base station, data, through acore network, to the first target base station and the second targetbase station respectively, the data include a PDCP SDU of data of acorresponding service, which has been sent without receiving an ACK orwith a NACK received (type 1), or data of a service data unit (SDU)(i.e., without a PDCP SN) (type 2); or

the source base station forwards a PDCP SDU of data corresponding to allservices being handed over, an ACK of which is not received or a NACK ofwhich is received (type 1), or data of an SDU (i.e., without a PDCP SN)(type 2) to the first target base station, and then the first targetbase station forwards a PDCP SDU of data corresponding to a service ofthe second target base station, an ACK of which is not received or aNACK of which is received (type 1), or data of SDU (i.e., without PDCPSN) (type 2) to the second target base station.

In an uplink direction, the UE, starting from a first PDCP SDU packet ofeach service, an acknowledgement of which is not received, resends anuplink PDCP SDU without receiving an ACK to the corresponding firsttarget base station and the second target base station. When receiving abitmap, the UE may determine, according to a presentation of the bitmap,an ACK with an acknowledgement received, and send data without receivingan ACK to corresponding first target base station and the second targetbase station. The UE may also send, starting from a first PDCP SDUpacket without receiving an acknowledgement, all latter data to thecorresponding first target base station and the second target basestation.

Step 309, the source base station forwards, according to conditions ofservice undertaken by cells in the first target base station and thesecond target base station, SN STATUS TRANSFER (SN status transferinformation) of corresponding services, through the core network, to thefirst target base station and the second target base stationrespectively, and indicates a receiving status of uplink data and/or asending status of downlink data of a corresponding RAB in the SN statustransfer information, for example, notifying of a serial number (SN) ofa first packet of type 2, an SN number of a first lost UL data packetand a bitmap of a UL data packet of the target base station; or

the source base station, through the core network, forwards the SNSTATUS TRANSFER (SN status transfer information) corresponding to allservices being handed over to the first target base station; afterreceiving the SN STATUS TRANSFER corresponding to all services beinghanded over, the first target base station forwards SN status transferinformation of the services corresponding to the second target basestation to the second target base station, and indicates a receivingstatus of uplink data and/or a sending status of downlink data ofcorresponding RAB in the SN status transfer information, for example,notifying of an SN number of a first packet of type 2, an SN number of afirst lost UL data packet and a bitmap of a UL data packet of the targetbase station.

Step 310, after receiving the handover command message, the UEestablishes, according to information in the message mentioned in step307, a PDCP layer entity, an RLC layer entity, an MAC layer entity and aphysical layer entity corresponding to a cell protocol stack of thefirst target base station, and establishes a PDCP layer entity(optional), an RLC layer entity, an MAC layer entity and a physicallayer entity corresponding to the cell protocol stack of the secondtarget base station. After a radio bear is configured successfully, theUE forwards a PDCP SDU to a PDCP layer of the newly established cellprotocol stack of the first target base station and/or the second targetbase station, wherein the PDCP SDU is an unordered PDCP SDU of areordering buffer region in the PDCP entity in the UE protocol stackcorresponding to the source base station. After the forwarding iscompleted, the UE may release each layer entity corresponding to theprotocol stack of the source base station in the UE. The UE completes adownlink synchronization with the cell of the first target base stationand the cell of the second target base station. According to a preamblecode of a random access and RACH resource information in the handovercommand message, the UE initiates a random access process to the firsttarget base station to complete an uplink synchronization, and/orinitiates a random access process to the second target base station tocomplete an uplink synchronization. And then, the UE replies an RRCconnection reconfiguration completion message (HO confirm, or handoverconfirm) to the first target base station.

Step 311, after receiving the RRC connection reconfiguration completionmessage replied by the UE, the first target base station sends ahandover notify message to the MME and establishes a connection with theUE. At this time, the data transmission in the uplink direction in step308 may be implemented.

Step 312, after receiving the RRC connection reconfiguration completionmessage replied by the UE, the first target base station sends serviceconfiguration information of the UE or a handover indication message ofthe UE to the second target base station.

Step 313, after receiving the service configuration information of theUE or the handover indication message of the UE, the second target basestation sends a path switch request to the first target base station.The step is an optional step, and step 314 may be directly implementedafter step 312.

Step 314, the first target base station sends a path switch requestmessage to the MME, wherein the message includes: uplink and/or downlinkGTP tunnel endpoint information of the first target base station, uplinkand/or downlink GTP tunnel endpoint information of the second targetbase station and a corresponding identifier of an RAB, wherein the GTPtunnel endpoint information includes a transport layer address and a GTPTEID.

Step 315, the MME sends a modify bearer request (MODIFY BEARER REQUEST)message to a gateway (GW, for example, a serving gateway (S-GW), themessage includes uplink and/or downlink GTP tunnel endpoint informationof the first target base station, uplink and/or downlink GTP tunnelendpoint information of the second target base station and acorresponding identifier of an RAB, wherein the GTP tunnel endpointinformation includes a transport layer address and a GTP TEID.

Step 316, after receiving the MODIFY BEARER REQUEST message sent by theMME, the Serving Gateway switches an RAB, in need of a path switching,to the corresponding first target base station and/or the second targetbase station respectively. And then, the Serving Gateway sends an endmarker packet to the source base station and releases a path with thesource base station.

Step 317, after receiving the end marker packet, the source base stationrespectively forwards, according to conditions of services undertaken bycells of a main base station and an auxiliary base station, an endmarker packet of a corresponding service to the first target basestation and the second target base station; or

the source base station sends end marker packets corresponding to allservices being handed over to the first target base station, and thenthe first target base station forwards an end marker packet of a servicecorresponding to the second target base station to the second targetbase station.

Step 318, after detecting an end marker packet, the first target basestation and/or the second target base station sequentially receives datasent by the Serving Gateway and data forwarded by the source basestation.

Step 319, the Serving Gateway sends a modify bearer response (MODIFYBEARER RESPONSE) to the MME.

Step 320, after receiving the modify bearer response message sent by theServing Gateway, the MME sends a UE context deletion command message tothe source base station.

Step 321, after receiving the UE context deletion command message sentby the MME, the source base station deletes the context of the UE in thesource base station and replies a UE context deletion completion messageto the MME.

Step 322, the MME sends a path switch request acknowledge (PATH SWITCHREQUEST ACKNOWLEDGE) message to the first target base station.

Step 323, the first target base station sends a path switch requestacknowledge (PATH SWITCH REQUEST ACKNOWLEDGE) message to the secondtarget base station.

Step 314 to step 323 belong to a transmission of a data plane.

By means of the embodiment, the UE is handed over from the source basestation to the first target base station and the second target basestation.

Embodiment 4

The embodiment further provides a method for handing over a UE to multicells. In the embodiment, the UE is handed over from a base station to atarget base station 1 (first target base station) providing a cellaggregation service and an auxiliary target base station 2 (secondtarget base station).

FIG. 4 is a schematic diagram of a handover processing method accordingto the embodiment 4 of the present invention. As shown in FIG. 4, themethod as shown in the embodiment includes following steps.

Step 401, through a handover decision, the source base stationdetermines to hand over the UE to the first target base station, and abasis of the decision may be a measurement report of the UE. And then,the source base station sends a handover request message to the firsttarget base station, wherein optional parameters carried in the handoverrequest message include at least one of followings: information of arecommended target cell group (for example, information and cellinformation of the first target base station and/or the second targetbase station), a measurement report of cells of the adjacent basestations, RRC context information of the UE, context information of anS1 interface of the UE, E-RAB information and the like.

In the step, the source base station may also determine to hand over theUE to the first target base station and/or the second target basestation simultaneously. At this time, the handover request message mayinclude: information of a recommended target cell group (information andcell information of the first target base station and/or the secondtarget base station), RRC context information of the UE, contextinformation of an S1 interface of the UE and information of an RAB,namely, the handover request message may include no measurement reporton cells of the two base stations. If the source base station merelydetermines, according to the measurement report on the UE, to hand overthe UE to the first target base station, the measurement report on thecell of the second target base station may be carried in the handoverrequest message, for enabling the first target base station todetermine, according to the measurement report, to hand over the UE tothe first target base station and the second target base stationsimultaneously. At this time, the handover request message may include:information of a recommended target cell group (information and cellinformation of the first target base station), measurement report oncells of the two base stations, RRC context information of the UE,context information of an S1 interface of the UE and information of anRAB.

Step 402, after receiving the handover request message, the first targetbase station sends a first message (the message may be called as aresource status detection message) to the second target base stationaccording to at least one of following contents, notifying the secondtarget base station of the handover of part or all of a service of theUE to the second target base station is to be performed (a contentnotified may include: service information, split information,information of the UE to be allocated to the second target base station(for example, E-RAB information) and the like), a recommended targetcell group (namely, the first target base station and the second targetbase station), a result of a measurement report of the UE on cells ofthe two base stations, according a condition of a resource of anauxiliary base station known by the first target base station and RABinformation of the UE.

Optionally, the resource status detection message may include radio bearconfiguration information corresponding to E-RAB information of the UE,for example, if the allocation is performed by first target base stationactively, the message may include following information:

an identifier of the UE (for example, a C-RNTI or an XmAP identifier);and

split indication information, wherein the split indication informationincludes data split information based on an RB or data split informationbased on a packet.

The resource status detection message may further include serviceinformation of at least one service. The service information includesquality information of a service and/or configuration information of anRB. The resource status detection message instructs the second targetbase station to perform a resource configuration according to serviceinformation of the at least one service, wherein the second target basestation is at least one base station in a base station providing aservice to the UE (such as the first target base station and the secondtarget base station).

Optionally, the data split information based on the RB means that thefirst target base station sends SDU data of a PDCP layer of a service ofthe UE to the second target base station. At this time, after receivingthe information of at least one service, the second target base stationmay perform corresponding resource configuration for the information ofat least one service, to configure a PDCP layer, an RLC layer, an MAClayer and a physical layer of an RB corresponding to the information ofat least one service. The data split information based on the packetrefers to SDU data of an RLC layer of a service of the UE sent from thefirst target base station to the second target base station. At thistime, after receiving at least one service information, the secondtarget base station may perform corresponding resource configuration forthe at least one service information, to configure an RLC layer, an MAClayer and a physical layer of an RB corresponding to the at least oneservice information.

Optionally, when the split indication information includes the datasplit information based on the packet, the second target base stationconfigures, according to information of at least one service, an RLClayer, an MAC layer and a physical layer of an RB corresponding to theat least one service, and the first target base station configures aPDCP layer, an RLC layer, an MAC layer and a physical layer of the RB.

A configuration message is sent to the UE, for enabling the UE toconfigure a corresponding RB according to the configuration message,wherein the configuration message includes configuration listinformation of the RB and/or information of a cell of the second targetbase station.

Optionally, the configuration information of the RB includes: theconfiguration information of a PDCP layer, an RLC layer, an MAC layerand a physical layer, or configuration information of an RLC layer, anMAC layer and a physical layer.

In this way, the second target base station may configure the PDCPlayer, the RLC layer, the MAC layer and the physical layer, or the RLClayer, the MAC layer and the physical layer of the RB corresponding tothe service information of at least one service.

Optionally, the service information may further include at least one offollowing items: configuration coordination information of a radioresource of RB, an identifier of RB, an identifier of RAB and splitindication information.

Optionally, the configuration coordination information of the radioresource of the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation and space domain information, wherein the frequency domaininformation may include but not limited to position information of aphysical resource block, the space domain information may include butnot limited to wave beam information, flow information and spatialencoding matrix information, and the code domain information may includebut not limited to an address code, a scrambling code and a sequenceinitializing code.

Step 403, the second target base station sends a resource statusdetection response message to the first target base station.

If the second target base station accepts the handover request, namely,the second target base station accepts the handover of part or all of aservice of the UE to the second target base station, the resource statusdetection response message includes a confirmation or a modification ofa configuration content in the resource status detection message. Forexample, through a resource status detection message, the first targetbase station notifies the second target base station that the handoverof multiple services of the UE to the second target base station is tobe performed, the second target base station agrees the handover of partof services in the multiple services to the second target base station,and notified the first target base station, by a resource statusdetection response message, of handing over the part of services in themultiple service, which is agreed by the second target base station, tothe second target base station.

Optionally, the resource status detection response message may includeradio bear configuration information corresponding to E-RAB informationof the UE, for example, if the allocation is performed by the secondtarget base station actively, the message may include followinginformation:

an identifier of the UE (for example, a C-RNTI or an XmAP identifier);and

split indication information, wherein the split indication informationincludes data split information based on an RB or data split informationbased on a packet.

The resource status detection response message may further includeservice information of at least one service, wherein the serviceinformation includes quality information of a service and/orconfiguration information of an RB.

The resource status detection response message may further include atleast one of followings:

first information and indication information, wherein the firstinformation includes at least one of followings: information on refusinga handover of part or all of a service of the user equipment to thesecond target base station, information on accepting the handover ofpart or all of a service of the user equipment to the second target basestation, or information on modifying the first message, and theindication information includes at least one of followings: anidentifier of an RB accepted by the second target base station,configuration information of an RB accepted by the second target basestation, an identifier of an RAB corresponding to an RB accepted by thesecond target base station, an identifier of an RB whose resourceconfiguration is rejected by the second target base station, and anidentifier of an RAB corresponding to an RB whose resource configurationis rejected by the second target base station.

The resource status detection response message may further include atleast one of followings:

fourth type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station (forexample, the third GTP tunnel endpoint information), wherein the fourthtype of GTP tunnel endpoint information is used for establishing atransmission bearer for forwarding data between the first target basestation and the second target base station;

second type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station (forexample, sixth GTP tunnel endpoint information), wherein the second typeof GTP tunnel endpoint information is used for establishing atransmission bearer for forwarding data between the second target basestation and the source base station;

third type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepting by the second target base station,wherein the third type of GTP tunnel endpoint information is used forrequesting a core network node to convert a GTP tunnel endpoint.

Optionally, the configuration information of the RB includes:configuration information of a PDCP layer, an RLC layer, an MAC layerand a physical layer, or configuration information of an RLC layer, anMAC layer and a physical layer. In this way, the second target basestation may configure the PDCP layer, the RLC layer, the MAC layer andthe physical layer, or the RLC layer, the MAC layer and the physicallayer of an RB corresponding to the service information of at least oneservice.

Optionally, the service information may further include at least one ofthe following items: configuration coordination information of a radioresource of an RB, an identifier of an RB, an identifier of an RAB andsplit indication information.

Optionally, the configuration coordination information of the radioresource of the RB includes at least one of following items: a physicalcell identifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation and space domain information; wherein the frequency domaininformation may include but not limited to position information of aphysical resource block; the space domain information may include butnot limited to wave beam information, flow information and spatialencoding matrix information; the code domain information may include butnot limited to an address code, a scrambling code and a sequenceinitializing code.

A PDCP entity of the UE is logically corresponding to a PDCP entity ofthe first target base station, a first RLC entity and a second RLCentity of the UE are logically corresponding to RLC entities of thefirst target base station and the second target base stationrespectively, a first MAC entity and a second MAC entity of the UE arelogically corresponding to MAC entities of the first target base stationand the second target base station respectively.

If the second target base station rejects the handover request message,the resource status detection response message includes a refusal to aconfiguration content in the resource status detection message, forexample, the resource status detection response message includesinformation on refusing the handover of the UE to the second target basestation.

Step 404, the first target base station sends a Handover Request ACKmessage to the source base station, and the message includes: a UEidentifier, E-RAB information, radio bear information, uplink and/ordownlink GTP tunnel endpoint information of the first target basestation (including a transport layer address and a GTP TEID), and uplinkand/or downlink GTP tunnel endpoint information of the second targetbase station (including a transport layer address and a GTP TEID),wherein the radio bear information includes a content of the message instep 403. A step is implemented after this step.

The handover request acknowledge message may include at least one offollowings:

an identifier of the UE allocated at the source base station, anidentifier of the UE allocated at the first target base station and/orthe second target base station, a first transparent containerconfiguration, an identifier of at least one RAB rejected by the firsttarget base station and/or the second target base station, an identifierof at least one RAB accepted by the first target base station, fifthtype of GTP tunnel endpoint information corresponding to an identifierof at least one RAB accepted by the first target base station, anidentifier of at least one RAB accepted by the second target basestation, sixth type of GTP tunnel endpoint information corresponding toan identifier of at least one RAB accepted by the second target basestation, second type of GTP tunnel endpoint information corresponding toan identifier of an RAB accepted by the second target base station, anda corresponding relation between at least one RAB accepted by the firsttarget base station and/or the second target base station and the firsttarget base station and/or the second target base station,

wherein the fifth type of GTP tunnel endpoint information (for example,fourth GTP tunnel endpoint information) is used for establishing atransmission bearer for data forwarding between the first target basestation and the source base station; the sixth type of GTP tunnelendpoint information (for example, fifth GTP tunnel endpointinformation) is used for establishing a transmission bearer forforwarding data between the first target base station and the sourcebase station; and the second type of GTP tunnel endpoint information isused for establishing a transmission bearer for data forwarding betweenthe second target base station and the source base station.

Preferably, the first transparent container configuration may include atleast one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station;

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

Preferably, the configuration information of the RB includes at leastone of the following items: configuration information of a PDCP entitycorresponding to the RB, configuration information of at least one RLCentity corresponding to the RB, MAC configuration informationcorresponding to each RLC entity corresponding to the RB, logic channelconfiguration message, physical layer configuration information, anidentifier of a service, split indication information and configurationinformation of a radio source corresponding to the RB.

The configuration information of the radio source corresponding to theRB includes at least one of followings:

a physical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information and space domain information,wherein the frequency domain information may include but not limited toposition information of a physical resource block; the space domaininformation may include but not limited to wave beam information, flowinformation and spatial encoding matrix information; the code domaininformation may include but not limited to an address code, a scramblingcode and a sequence initializing code.

Step 405, after receiving the HANDOVER REQUEST ACKNOWLEDGE, the sourcebase station sends a handover command message (for example, sending inthe form of an RRC connection reconfiguration message) to the UE, andthe handover command message includes: information of a target cellgroup (for example, information and cell information of the first targetbase station and the second target base station), configurationinformation of a service in the two base stations (the radio bearinformation includes a content of the message in step 403), securityinformation and the like.

It should be noted that, as long as the source base station receives theHandover Request ACK (HANDOVER REQUEST ACKNOWLEDGE), or as long as thesource base station starts to send the handover command to the UE, aforwarding of data begins. Therefore, in this step, after receiving theHANDOVER REQUEST ACKNOWLEDGE, the source base station may execute a datatransmission in a downlink direction in step 406 and step 407, whereinthe executing sequence of step 406 and step 407 is not limited.

Step 406, in a downlink direction, the source base station sends,according to conditions of services undertaken by cells in the firsttarget base station and the second target base station, a PDCP SDU ofdata of a corresponding service, which has been sent without receivingan ACK or with a NACK received (type 1), to the first target basestation and/or the second target base station corresponding to theservice respectively, and forwards data of an SDU (i.e., without PDCPSN) (type 2) to the first target base station and/or the second targetbase station corresponding to the service; or

the source base station forwards a PDCP SDU of data corresponding to allservices being handed over, an ACK of which is not received or a NACK ofwhich is received (type 1) or data of an SDU (i.e., without PDCP SN)(type 2) to the first target base station. After receiving these data,the first target base station forwards a PDCP SDU corresponding to aservice of the second target base station, an ACK of which is notreceived or a NACK of which is received (type 1), or data of SDU (i.e.,without PDCP SN) (type 2) to the second target base station.

In an uplink direction, the UE, starting from a first PDCP SDU packet ofeach service, an acknowledgement of which is not received, resends anuplink PDCP SDU without receiving an ACK to the corresponding firsttarget base station and the second target base station.

Step 407, the source base station sends, according to conditions ofservice undertaken by cells in the first target base station and thesecond target base station, SN STATUS TRANSFER (SN status transferinformation) of corresponding services to the first target base stationand the second target base station respectively, and indicates areceiving status of uplink data and/or a sending status of downlink dataof a corresponding RAB in the SN status transfer information, forexample, notifying of an SN number of a first packet of type 2, an SNnumber of a first lost UL data packet and a bitmap of a UL data packetof the target base station (the first target base station and/or thesecond target base station); or

the source base station sends the SN STATUS TRANSFER (SN status transferinformation) corresponding to all services being handed over to thefirst target base station; after receiving the SN STATUS TRANSFERcorresponding to all services being handed over, the first target basestation forwards SN status transfer information of the servicescorresponding to the second target base station to the second targetbase station, and indicates a receiving status of uplink data and/or asending status of downlink data of the corresponding RAB in the SNstatus transfer information, for example, notifying of an SN number of afirst packet of type 2, an SN number of a first lost UL data packet anda bitmap of a UL data packet of the target base station.

Step 408, after receiving the handover command message, the UErespectively establishes, according to a configuration parameter of aservice in the message, a new PDCP layer entity, RLC layer entity, MAClayer entity and physical layer entity for a bearer corresponding to acell protocol stack of the first target base station, and establishes anew PDCP layer entity (optional), RLC layer entity, MAC layer entity andphysical layer entity for a bearer corresponding to the UE and a cellprotocol stack of the second target base station. After a radio bear isconfigured successfully, the UE forwards an unordered PDCP SDU in areordering buffer region in the PDCP entity in the protocol stackcorresponding to the source base station to a newly established PDCPlayer of the cell protocol stack of the first target base station and/orthe cell protocol stack of the second target base station. After theforwarding is completed, the UE may release each layer entitycorresponding to the protocol stack of the source base station in theUE. The UE completes a downlink synchronization with the cell of thefirst target base station and the cell of the second target basestation. According to a preamble code of a random access and randomaccess channel (RACH) resource information in the handover commandmessage, the UE initiates a random access process to the first targetbase station to complete an uplink synchronization, and/or initiates arandom access process to the second target base station to complete anuplink synchronization. And then, the UE sends an RRC connectionreconfiguration completion message to the first target base station.

Step 409, after receiving the RRC connection reconfiguration completionmessage sent by the UE, the first target base station sends serviceconfiguration information of the UE or handover indication informationof the UE to the second target base station, to instruct the secondtarget base station to start to use a resource it configured for the UE.

Step 410, after receiving the service configuration information of theUE or the handover indication information of the UE, the second targetbase station sends a handover indication reply message to the firsttarget base station. This step is optional.

Step 411, the first target base station sends a path switch requestmessage to an MME, wherein the message includes: uplink and/or downlinkGTP tunnel endpoint information of the first target base station(including a transport layer address and a GTP TEID) and a correspondingidentifier of an RAB, uplink and/or downlink GTP tunnel endpointinformation of the second target base station (including a transportlayer address and a GTP TEID) and a corresponding identifier of an RAB.

Step 412, the MME sends a MODIFY BEARER REQUEST message to a ServingGateway, and the message includes: uplink and/or downlink GTP tunnelendpoint information of the first target base station (including atransport layer address and a GTP TEID) and a corresponding identifierof an RAB, uplink and/or downlink GTP tunnel endpoint information of thesecond target base station (including a transport layer address and aGTP TEID) and a corresponding identifier of an RAB.

Step 413, after receiving the MODIFY BEARER REQUEST message sent by theMME, the Serving Gateway switches an RAB, in needing of a pathswitching, to the corresponding first target base station and/or thesecond target base station respectively. And then, the Serving Gatewaysends an end marker packet to the source base station and releases apath with the source base station.

Step 414, after receiving the end marker packet, the source base stationrespectively forwards, according to conditions of services undertaken bycells of the first target base station and the second target basestation, an end marker packet of a corresponding service to the firsttarget base station and the second target base station; or

the source base station sends end marker packets corresponding to allservices being handed over to the first target base station, and thenthe first target base station forwards end marker packets of a servicecorresponding to the second target base station to the second targetbase station.

Step 415, after detecting an end marker packet, the first target basestation and/or the second target base station sequentially receives datasent by the Serving Gateway and data forwarded by the source basestation.

Step 416, the Serving Gateway sends a MODIFY BEARER RESPONSE to the MME.

Step 417, the MME sends a PATH SWITCH REQUEST ACKNOWLEDGE message to thefirst target base station.

Step 418, the first target base station sends a PATH SWITCH REQUESTACKNOWLEDGE message to the second target base station.

By means of the embodiment, the UE is handed over from the source basestation to the first target base station and the second target basestation.

Embodiment 5

The embodiment provides a handover processing method. The method may beused for a handover without a loss of data under a multi-cell splitscenario, for example, handing over a UE from multiple source basestations to a target base station.

FIG. 5 is a flowchart of a handover processing method according to theembodiment 5 of the present invention, as shown in FIG. 5, the methodincludes:

step 501, sending, by a first source base station, a handover requestmessage to a target base station, to make a request for a handover of auser equipment from the first source base station and a second sourcebase station to the target base station;

step 502, receiving, by the first source base station, a handoverrequest acknowledge message sent by the target base station; and

step 503, sending, by the first source base station, a handover commandmessage to the user equipment, to notify the user equipment to hand overfrom the first source base station and the second source base station tothe target base station.

In the solution, through the handover request message, the first sourcebase station notifies the target base station that the UE is handed overfrom the first source base station and the second source base station tothe target base station, so that the UE may be handed over from multiplesource base stations to one target base station, a normal handoveroperation without a loss of data under a multi-cell split scenario isachieved, and the supporting problem that the handover without the lossof data under the multi-cell split scenario could not be supported inthe conventional art that is solved.

Preferably, before the first source base station sends the handoverrequest message to the target base station, the first source basestation sends a handover initiation request message to the second sourcebase station, to make a request for a handover of the user equipmentfrom the second source base station to the target base station; thefirst source base station receives a handover initiation responsemessage from the second source base station, and generates the handoverrequest message according to the handover initiation response message.

Preferably, before the first source base station sends the handoverrequest message to the target base station, the first source basestation may send a handover initiation request message to the secondsource base station through a local gateway; the second source basestation sends the handover initiation response message to the localgateway, and then, the local gateway generates the handover requestmessage according to a handover initiation response message and sendsthe handover request message to the first source base station.

After the first source base station receives the handover requestacknowledge message sent by the target base station, the first sourcebase station may send a handover execution notification message to thesecond source base station, for notifying the second source base stationto start executing a handover operation. The handover executionnotification message may be a command message, for commanding the secondsource base station to perform the handover and it may also be a requestmessage, for requesting the second source base station to perform thehandover.

Preferably, after the first source base station sends the handoverexecution notification message to the second source base station, thefirst source base station receives a handover execution notificationresponse message from the second source base station, wherein thehandover execution notification response message includes: SN statustransfer information corresponding to at least one RAB served by thesecond source base station, and/or a data packet, in need of forwarding,corresponding to at least one RAB served by the second source basestation.

Preferably, after the first source base station receives the handoverrequest acknowledge message sent by the target base station, the firstsource base station and/or the second source base station sends dataand/or signaling of the user equipment to the target base station.Therefore, the handover request acknowledge message may be used fortriggering the first source base station and/or the second source basestation to send data and/or signaling of the user equipment to thetarget base station. In the handover process of the embodiment, thefirst source base station and/or the second source base station send(s)data and/or signaling of the user equipment to the target base station,in order to realize a handover without a loss of data.

In a preferable implementation manner of the embodiment of the presentinvention, the sending, by the first source base station and/or thesecond source base station, the data and/or signaling of the userequipment to the target base station, includes:

sending, by the first source base station, data and/or signaling of theuser equipment in the first source base station and the second sourcebase station to the target base station; or

sending, by the first source base station, data and/or signaling of theuser equipment in the first source base station to the target basestation, and sending, by the second source base station, data and/orsignaling of the user equipment in the second source base station to thetarget base station,

wherein the data and/or signaling of the user equipment include(s) atleast one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data of aservice corresponding to the user equipment with a NACK received, SDUdata, serial number SN status transfer information and an end markerpacket,

wherein, the first source base station and the second source basestation may send the end marker packet to the target base station aftersending the data of the UE therein to the target base station.

Preferably, before the first source base station sends the end markerpacket to the target base station, the first source base station mayreceive the end marker packet sent by an S-GW,

wherein, the first source base station may send the handover requestmessage to the target base station through a local gateway,

wherein the second source base stations may be more than one.

In the embodiment, when there exist multiple source base stations of theUE, one source cell therein (namely, the first source cell) sends arequest to the target base station to make a request for a handover ofthe UE from multiple source cells to a target cell, thereby realizingthe handover of the UE from multiple source cells to one target cell.

Embodiment 6

The embodiment provides a handover processing method, and the method maybe used for a handover without a loss of data under a multi-cell splitscenario, for example, a handover of a UE from multiple source basestations to a target base station.

FIG. 6 is a flowchart of a handover processing method according to theembodiment 6 of the present invention. As shown in FIG. 6, the methodincludes:

step 601, receiving, by a target base station, a handover requestmessage sent by a first source base station, wherein the handoverrequest message is used for making a request for a handover of a userequipment from the first source base station and a second source basestation to the target base station; and

step 602, sending, by the target base station, a handover requestacknowledge message to the first source base station, wherein thehandover request acknowledge message is used for indicating that thetarget base station accepts the handover of the user equipment from thefirst source base station and the second source base station to thetarget base station.

Preferably, after the target base station sends the handover requestacknowledge message to the first source base station, the target basestation receives data and/or signaling of the user equipment sent by thefirst source base station and/or the second source base station.

The receiving, by the target base station, the data and/or signaling ofthe user equipment sent by the first source base station and/or thesecond source base station, may include:

receiving, by the target base station, the data and/or signaling of theuser equipment sent by the first source base station, and/or receivingthe data and/or signaling of the user equipment sent by the secondsource base station; or

receiving, by the target base station, the data and/or signaling of theuser equipment corresponding to the first source base station and/or thesecond source base station, sent by the first source base station.

Preferably, the data and/or signaling of the user equipment include(s)at least one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data of aservice corresponding to the user equipment which a NACK received, SDUdata, serial number SN status transfer information and an end markerpacket.

Optionally, the target base station may receive the handover requestmessage, which comes from the first source base station, forwarded by alocal gateway.

wherein, after the target base station sends the handover requestacknowledge message to the first source base station, the method mayfurther include: receiving, by the target base station, a radio resourcecontrol RRC connection reconfiguration completion message sent by theuser equipment, and establishing a connection with the user equipment.

In the embodiment, when there exist multiple source base stations of theUE, one source cell therein (namely, the first source cell) sends arequest to the target base station to make a request for a handover ofthe UE from multiple source cells to a target cell, thereby realizingthe handover of the UE from multiple source cells to one target cell.

Embodiment 7

In the embodiment, a UE is handed over from a source base station 1(namely, the first source base station) providing a cell aggregationservice and an auxiliary source base station 2 (namely, the secondsource base station) to a target base station, wherein there is aconnecting interface between the target base station and a gateway.

FIG. 7 is a schematic diagram of a handover processing method accordingto embodiment 7 of the present invention, as shown in FIG. 7, the methodincludes following steps.

Step 701, through a handover decision, the first source base stationdetermines to hand over UE from the first source base station and thesecond source base station to the target base station, and sends ahandover request message to the target base station, wherein parameterscarried in the message may include: information and cell information ofthe first source base station, RRC context information of the UE,context information of an S1 interface of the UE and E-RAB information,and optional parameters carried in the message may further include atleast one of followings: information and cell information of the secondsource base station, and respective radio bear configuration andmeasurement configuration information of the UE in the first source basestation and the second source base station.

Preferably, before sending the handover request message to the targetbase station, the first source base station may also implement followingsteps.

The first source base station sends a message (the message may be calledas a handover initiation request message) to the second source basestation, to notify that a handover is to be initiated, for example,notifying of a handover of the user equipment from the second sourcebase station to the target base station, wherein the handover initiationrequest message carries cell information of the target base station.

The second source base station sends a message (the message may becalled as a handover initiation response message) to the first sourcebase station, for notifying the first source base station of theinformation which is used by the second source base station to serve theUE, for example, the message may carry following parameters:configuration information of the UE, and these parameters may be usedfor creating a handover request message.

In addition, if the first source base station contains serviceinformation of the second source base station, the handover requestmessage may be created directly without sending the handover initiationrequest message to the second source base station.

Step 702, after the target base station successfully accepts thehandover request message, namely, the target base station accepts thehandover of a service of the UE to the target base station, the targetbase station sends a Handover Request ACK message to the first sourcebase station, wherein the Handover Request ACK message includes: a UEidentifier, E-RAB information, radio bear information, uplink and/ordownlink GTP tunnel endpoint information of the target base station(including a transport layer address and a GTP TEID).

Step 703, after receiving the Handover Request ACK message, the firstsource base station sends a message (the message may be called as ahandover execution notification message) to the second source basestation, to notify the second source base station to start to execute ahandover operation.

It should be noted that, as long as the first source base stationreceives the Handover Request ACK (HANDOVER REQUEST ACKNOWLEDGE), or aslong as the first source base station starts to send a handover commandto the UE, a forwarding of data begins. Therefore, after this step, adata transmission in step 705 and step 706 may be executed.

In addition, when the handover execution notification message is acommand message, step 704 does not need to be implemented. At this time,the executing sequence of step 703 and step 707 is not limited. When thehandover execution notification message is a request message, aconfirmation of the second target base station is needed, namely, afterstep 703, step 704 is executed, and then step 707 is executed.

Step 704, after receiving the handover execution notification message,the second source base station sends a message (the message may becalled as a handover execution notification response message) to thefirst source base station. The message includes data of a servicecorresponding to the second source base station, which is in need ofbeing forwarded: a PDCP SDU of data which has been sent withoutreceiving an ACK or with a NACK received (type 1), or data of an SDU(i.e., without a PDCP SN) (type 2); and SN STATUS TRANSFER (SN statustransfer information) of a service corresponding to the second sourcebase station. A receiving status of uplink data and/or a sending statusof downlink data of a corresponding RAB is indicated in the SN statustransfer information, for example, notifying of an SN number of a firstpacket of type 2, an SN number of a first lost UL data packet and abitmap of a UL data packet of the target base station. (Step 704 isoptional)

Step 705, the first source base station sends SN STATUS TRANSFER (SNstatus transfer information) corresponding to all services being handedover to the target base station, and may indicate a receiving status ofuplink data and/or a sending status of downlink data of a correspondingRAB in the SN status transfer information for example, notifying of anSN number of a first packet of type 2, an SN number of a first lost ULdata packet and a bitmap of a UL data packet of the target base station.

Step 706, in a downlink direction, the first source base station sends aPDCP SDU of data corresponding to all services being handed over, an ACKof which is received or a NACK of which is received (type 1) to thetarget base station, and forwards the data of an SDU (i.e., without PDCPSN) (type 2) to the target base station.

In an uplink direction, the UE, starting from a first PDCP SDU packet ofeach service, an acknowledgement of which is not received, resends anuplink PDCP SDU to the corresponding target base station.

Step 707, after receiving a handover request response message (HANDOVERREQUEST ACKNOWLEDGE), the first source base station sends a handovercommand message (for example, sending in the form of an RRC connectionreconfiguration message) to the UE, and the message includes:information of a target cell (namely, information of the target basestation and a cell), configuration information of a service, securityinformation and the like.

Step 708, after receiving the handover command message, the UErespectively establishes, according to a configuration parameter of aservice in the message, a new PDCP layer entity, RLC layer entity, MAClayer entity and physical layer entity for a bearer corresponding to aprotocol stack of a target cell. After a radio bear is configuredsuccessfully, the UE forwards an unordered PDCP SDU in a reorderingbuffer region in a PDCP entity in a protocol stack corresponding tosource main and auxiliary base stations to a newly established PDCPlayer of the protocol stack of the target cell; after the forwarding iscompleted, the UE may release each layer entity corresponding to theprotocol stack of the source base station therein. The UE completesdownlink synchronization with a cell of the target base station.According to a preamble code of a random access and RACH resourceinformation in the handover command message, the UE initiates a randomaccess process to the target base station to complete uplinksynchronization. And then, the UE replies an RRC connectionreconfiguration completion message to the target base station.

Step 709, after receiving the RRC connection reconfiguration completionmessage replied by the UE, the target base station sends a Path SwitchRequest message to a core network node (an MME is taken as an examplefor illustration below).

Step 710, the MME sends a MODIFY BEARER REQUEST message to a gateway (aServing Gateway is taken as an example for illustration below), and themessage includes uplink and/or downlink GTP tunnel endpoint information,which includes a transport layer address and a GTP TEID of the targetbase station, and a corresponding identifier of an RAB.

Step 711, after receiving the MODIFY BEARER REQUEST message sent by theMME, the Serving Gateway switches an RAB, which needs a path switch,from the corresponding first source base station and/or second sourcebase station respectively to the target base station. And then, theServing Gateway sends an “end marker” packet to the first source basestation and the second source base station respectively, and releasespaths with the first source base station and the second source basestation.

Step 712, after receiving the end marker packet, the second source basestation forwards the received end marker packet to the first source basestation. Then, the first source base station sends an end marker packetcorresponding to all bearers being handed over to the target basestation.

Step 713, after receiving an end marker packet, the target base stationsequentially receives data sent by the Serving Gateway and dataforwarded by the source base stations.

Step 714, the Serving Gateway sends MODIFY BEARER RESPONSE to the MME.

Step 715, the MME sends a PATH SWITCH REQUEST ACKNOWLEDGE message to thetarget base station.

Through the embodiment, a handover of the user equipment from multiplesource cells to one target cell is realized.

Embodiment 8

FIG. 8 is a schematic diagram of a handover processing method accordingto the embodiment 8 of the present invention. As shown in FIG. 8, themethod includes following steps.

Step 801 to step 803, which are the same as step 701 to step 703.

Step 804, a second source base station sends a message (the message maybe called as a handover execution notification response message) to thefirst source base station, to notify the first source base station thatthe user equipment may be handed over from the second source basestation to a target base station.

It should be noted that, as long as the first source base stationreceives HANDOVER REQUEST ACKNOWLEDGE, or as long as the first sourcebase station starts to send a handover command to the UE, a forwardingof data begins. Therefore, after step 803, step 805, step 806 and step807 may be executed, wherein the executing sequence of step 805 to step807 is not limited.

Step 805, the first source base station sends SN STATUS TRANSFER (SNstatus transfer information), which is carried by a service itcorresponds, to the target base station, and indicates a receivingstatus of uplink data and/or a sending status of downlink data of acorresponding RAB in the SN status transfer information, for example,notifying of an SN number of a first packet of type 2, an SN number of afirst lost UL data packet and a bitmap of a UL data packet of the targetbase station.

Step 806, in a downlink direction, the first source base station sends aPDCP SDU of data of a service it corresponds, an ACK of which isreceived or a NACK of which is received (type 1), to the target basestation, and forwards data of an SDU (i.e., without a PDCP SN) (type 2)to the target base station.

In an uplink direction, the UE, starting from a first PDCP SDU packet ofeach service, an acknowledgement of which is not received, resends anuplink PDCP SDU to the corresponding target base station.

Step 807, the second source base station sends SN STATUS TRANSFER (SNstatus transfer information), which is carried by a service itcorresponds, to the target base station, and indicates a receivingstatus of uplink data and/or a sending status of downlink data of acorresponding RAB in the SN status transfer information, for example,notifying of an SN number of a first packet of type 2, an SN number of afirst lost UL data packet and a bitmap of a UL data packet of the targetbase station.

The second source base station may send the SN STATUS TRANSFER (SNstatus transfer information) carried by the service it corresponds tothe target base station by the triggering of indication information ofthe first source base station.

Step 808, in a downlink direction, the second source base station sendsa PDCP SDU of data carried by a service it corresponds, which has beensent without receiving an ACK or with a NACK received (type 1), to thetarget base station, and forwards data of an SDU (i.e., without a PDCPSN) (type 2) to the target base station.

In an uplink direction, the UE, starting from a first PDCP SDU packet ofa service, an acknowledgement of which is not received, resends anuplink PDCP SDU to a corresponding target base station.

Step 809, after receiving the HANDOVER REQUEST ACKNOWLEDGE, the firstsource base station sends a handover command message (for example,sending in a form of an RRC connection reconfiguration message) to theUE. The message includes: information of a target cell (for example,information of the target base station and a cell), configurationinformation of a service, security information and the like.

Step 810, after receiving the handover command message, the UErespectively establishes, according to a configuration parameter of theservice in the message, a PDCP layer entity, an RLC layer entity, an MAClayer entity and a physical layer entity corresponding to a protocolstack of a target cell. After a radio bear is configured successfully,the UE forwards an unordered PDCP SDU in a reordering buffer region in aPDCP entity in a protocol stack corresponding to the first source basestation and the second source base station to a newly established PDCPlayer of a cell protocol stack of the target base station. After theforwarding is completed, the UE may release each layer entitycorresponding to the protocol stack of the source base station. The UEcompletes downlink synchronization with a cell of the target basestation. According to a preamble code of a random access and RACHresource information in the handover command message, the UE initiates arandom access process to the target base station to complete uplinksynchronization. And then, the UE sends an RRC connectionreconfiguration completion message to the target base station.

Step 811, after receiving the RRC connection reconfiguration completionmessage sent by the UE, the target base station sends a Path SwitchRequest (path switch request) message to a core network node (an MME istaken as an example for illustration below).

Step 812, the MME sends a MODIFY BEARER REQUEST (modify bearer request)message to the gateway (a Serving Gateway is taken as an example forillustration below), and the message includes uplink and/or downlink GTPtunnel endpoint information (including a transport layer address and aGTP TEID) of the target base station and a corresponding identifier ofan RAB.

Step 813, after receiving the MODIFY BEARER REQUEST message sent by theMME, the Serving Gateway switches an RAB, which needs a path switch,from the corresponding first source base station and/or second sourcebase station respectively to the target base station. The Servinggateway respectively sends an “end marker” packet (an end marker packet)to the first source base station and the second source base stationrespectively, and then releases paths between it and the first sourcebase station, the second source base station.

Step 814, after the first source base station and the second source basestation receive the end marker packet sent by the Serving gateway, thesecond source base station forwards the received end marker packet tothe first source base station. Then, the first source base station sendsan end marker packets corresponding to all bearers being handed over tothe target base station.

Step 815, after receiving an end marker packet, the target base stationsequentially receives data sent by the Serving GW and data forwarded bythe source base stations.

Step 816, the Serving Gateway sends a MODIFY BEARER RESPONSE (modifybearer response) message to the MME.

Step 817, the MME sends a PATH SWITCH REQUEST ACKNOWLEDGE (path switchrequest acknowledge) message to the target base station.

Through the embodiment, a handover of the user equipment from multiplesource cells to one target cell is realized.

Embodiment 9

FIG. 9 is a schematic diagram of a handover processing method accordingto the embodiment 9 of the present invention. As shown in FIG. 9, themethod shown in the embodiment includes following steps.

Step 901, a local gateway (a residential gateway) in a source networkside sends a handover request message to a target base station.Parameters carried in the message include: information and cellinformation of a first source base station, RRC context information ofUE, context information of an S1 interface of the UE and E-RABinformation. Preferably, the message may also carry at least one offollowing parameters: information and cell information of a secondsource base station and radio bear configuration, and respectivemeasurement configuration information of the UE in the first source basestation and the second source base station.

Optionally, before the local gateway in the source network side sendsthe handover request message to the target base station, theabove-mentioned method may further include followings.

Through a handover decision, a handover to the target base station isdetermined by the first source base station. Then the first source basestation sends an handover first request message to the local gateway, tonotify that a handover of user equipment from the second source basestation to the target base station is to be initiated. The handoverfirst message carries information of the target base station and a cell.The local gateway forwards the message to the second source basestation.

The second source base station replies an handover first responsemessage to the local gateway, wherein it may carry a parameter:configuration information of the UE, and the handover first responsemessage may be used for generating a handover request message.

Step 902, after receiving the handover request message, if the targetbase station can accept the UE, the target base station sends a HandoverRequest ACK message to the local gateway in the source network side. Themessage includes: a UE identifier, E-RAB information, radio bearinformation, uplink and/or downlink GTP tunnel endpoint informationincluding a transport layer address and a GTP TEID of the target basestation.

Step 903, after receiving the Handover Request ACK message, the localgateway in the source network side forwards the message to the firstsource base station.

Step 904, after receiving the Handover Request ACK message, the firstsource base station sends a handover command message (RRC connectionreconfiguration message) to the UE, and sends a handover executionnotification message to the local gateway. The handover command messageincludes at least one of followings: information of a target cell(namely, information of the target base station and cell information ofthe target base station), configuration information of a service andsecurity information. The execution notification message includes dataof a service corresponding to the first source base station, which is inneed of being forwarded. The data include: a PDCP SDU of sent data whichhas been sent without receiving an ACK or with a NACK received (type 1),data of an SDU (i.e., without a PDCP SN) (type 2), and SN STATUSTRANSFER (SN status transfer information) of a service corresponding tothe first source base station. A receiving status of uplink data and/ora sending status of downlink data of a corresponding RAB is indicated inthe SN status transfer information, for example, notifying of an SNnumber of a first packet of type 2, an SN number of a first lost UL datapacket and a bitmap of a UL data packet of the target base station. Andthen, the local gateway in the source network side forwards the handoverexecution notification message to the second source base station, tonotify the second source base station to start to execute a handoveroperation.

Step 905, the second source base station replies a handover executionnotification response message to the local gateway, the messageincludes: data of a service corresponding to the second source basestation, which is in need of being forwarded. The data include: a PDCPSDU of data which has been sent without receiving an ACK or with a NACKreceived (type 1), data of an SDU (i.e., without a PDCP SN) (type 2),and SN STATUS TRANSFER (SN status transfer information) of a servicecorresponding to the second source base station, wherein the SN statustransfer information may indicate a receiving status of uplink dataand/or a sending status of downlink data of a corresponding RAB, forexample, notifying of an SN number of a first packet of type 2, an SNnumber of a first lost UL data packet and a bitmap of a UL data packetof the target base station.

Step 906, as long as the first source base station receives HANDOVERREQUEST ACKNOWLEDGE, or as long as the source base station starts tosend handover command to the UE, a forwarding of data begins.

The local gateway in the source network side sends SN STATUS TRANSFER(SN status transfer information) corresponding to all services beinghanded over to the target base station, and indicates a receiving statusof uplink data and/or a sending status of downlink data of acorresponding RAB in the SN status transfer information, for example,notifying of an SN number of a first packet of type 2, an SN number of afirst lost UL data packet and a bitmap of a UL data packet of the targetbase station.

The local gateway in the source network side sends a PDCP SDU of datacorresponding to all services being handed over, which has been sentwithout receiving an ACK or with a NACK received, to the target basestation (type 1), and forwards data of an SDU (i.e., without a PDCP SN)(type 2) to the target base station.

In an uplink direction, the UE, starting from a first PDCP SDU packetwithout receiving an acknowledgement (ACK) of each service, resends anuplink PDCP SDU without receiving an acknowledgement to thecorresponding target base station.

Step 907, after receiving the handover command message, the UErespectively establishes, according to a configuration parameter of aservice in the handover command message, a PDCP layer entity, an RLClayer entity, an MAC layer entity and a physical layer entitycorresponding to the protocol stack of a target cell. After a radio bearis configured successfully, the UE forwards an unordered PDCP SDU in areordering buffer region in a PDCP entity in a protocol stackcorresponding to the first source base station and the second sourcebase station to a newly established PDCP layer of the cell protocolstack of the target base station. After the forwarding is completed, theUE may release each layer entity corresponding to a protocol stack ofthe source base station in the UE. According to a 1 preamble code of arandom access and a random access channel (RACH) resource information inthe handover command message, the UE initiates a random access processto the target base station to complete an uplink synchronization, andsends an RRC connection reconfiguration completion message to the targetbase station.

Step 908, after the target base station receives the RRC connectionreconfiguration completion message, the local gateway may send a PathSwitch Request message to the MME.

Step 909, an MME sends a MODIFY BEARER REQUEST message to the ServingGateway, and the message includes uplink and/or downlink GTP tunnelendpoint information, which includes a transport layer address and a GTPTEID of the target base station, and a corresponding identifier of anRAB.

Step 910, after receiving the MODIFY BEARER REQUEST message sent by theMME, the Serving Gateway switches an RAB, which needs a path switch,from the corresponding first source base station and the second sourcebase station respectively to the corresponding target base station. TheServing Gateway respectively sends an “end marker” packet to the localgateway in the source network side and releases paths between it and thefirst source base station, the second source base station.

Step 911 (optional), the local gateway in the source network sideforwards an “end marker” packet to the first source base station and asecond source auxiliary base station.

Step 912, after receiving an end marker packet, the local gateway in thesource network side sends an end marker packet corresponding to allbearers being handed over to the target base station.

Step 913, after receiving the end marker packet, the target base stationsequentially receives data sent by the Serving Gateway and dataforwarded by the source base stations (the first source base stationand/or the second source base station).

Step 914, the Serving Gateway sends MODIFY BEARER RESPONSE to the MME.

Step 915, the MME sends a PATH SWITCH REQUEST ACKNOWLEDGE message to thelocal gateway.

Through the embodiment, a handover of a user equipment from multiplesource cells to one target cell is realized.

Embodiment 10

The embodiment of the present invention further provides a base station,and the base station may be taken as a first target base station toachieve embodiments 1 to 4 of the above-mentioned method.

FIG. 10 is a block diagram of a structure of a base station according tothe embodiment 10 of the present invention. As shown in FIG. 10, thebase station includes a receiving unit 10 and a sending unit 12, wherein

the receiving unit is configured to receive a handover request messagesent by a source base station or a core network node;

the sending unit is configured to send, according to the handoverrequest message, a first message to a second target base station, tonotify the second target base station that a handover of part or all ofa service of a user equipment to the second target base station is to beperformed; and

the sending unit is further configured to send a handover requestacknowledge message to the source base station or the core network node,wherein the handover request acknowledge message is used for notifyingthe source base station or the core network node to hand over the userequipment to at least one target cell of the first target base stationand/or at least one target cell of the second target base station.

Preferably, the sending unit is configured to realize the sending,according to the handover request message, the first message to thesecond target base station in a following manner:

determining, according to a measurement report of the user equipmentand/or radio access bear RAB information of the user equipment in thehandover request message, that the handover of the part or all of theservice of the user equipment to a target cell of the second target basestation; or determining, according to information of a target cell ofthe second target base station in the handover request message, that thehandover of the part or all of the service of the user equipment to thesecond target base station; and

sending the first message to the second target base station.

The handover request message may include at least one of followings:information of at least one target cell of the second target basestation, measurement report information of the user equipment, contextinformation of the user equipment and information of a service of theuser equipment, wherein the information of the service includes RABinformation of the service.

Optionally, the first message includes: information of at least oneservice of the user equipment, wherein the information of the serviceincludes RAB information of the service and/or configuration informationof a radio bear RB.

Optionally, the information of the service further includes at least oneof followings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

Preferably, the GTP tunnel endpoint information is first type of GTPtunnel endpoint information or fourth type of GTP tunnel endpointinformation, wherein the first type of GTP tunnel endpoint informationis used for establishing a transmission bearer of an S1 interfacebetween a serving gateway S-GW and the first target base station and/orthe second target base station, and the fourth type of GTP tunnelendpoint information is used for establishing a transmission bearer forforwarding data between the first target base station and the secondtarget base station.

Preferably, the configuration information of the RB includes:

configuration information of a packet data convergence protocol PDCPlayer, a radio link control RLC layer, a medium access control MAC layerand a physical layer; or

configuration information of an RLC layer, an MAC layer and a physicallayer.

In one preferable implementation manner of the embodiment of the presentinvention, the receiving unit is further configured to receive a secondmessage sent by the second target base station after the first targetbase station sends the first message to the second target base station,wherein the second message is used for indicating information regardingwhether the handover of the part or all of the service of the userequipment to the second target base station is accepted by the secondbase station.

Preferably, the second message includes at least one of followings:

an identifier of the user equipment, first information and indicationinformation,

wherein the indication information includes at least one of followings:indication information of refusing the handover of the part or all ofthe service of the user equipment to the second target base station,indication information of accepting the handover of the part or all ofthe service of the user equipment to the second target base station, andindication information of modifying the first message;

the first information includes at least one of followings: an identifierof an RB accepted by the second target base station, configurationinformation of an RB accepted by the second target base station, anidentifier of an RAB corresponding to an RB accepted by the secondtarget base station, an identifier of an RB whose resource configurationis rejected by the second target base station, and an identifier of anRAB corresponding to an RB whose resource configuration is rejected bythe second target base station.

Preferably, the second message further includes at least one offollowings:

fourth type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station;

second type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe second type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between thesecond target base station and the source base station; and

third type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe third type of GTP tunnel endpoint information is used for requestinga core network node to convert a GTP tunnel endpoint.

The handover request acknowledge message may further include at leastone of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation between atleast one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

Optionally, the first transparent container configuration includes atleast one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

Optionally, the configuration information of the RB includes at leastone of followings:

configuration information of a PDCP entity corresponding to the RB,configuration information of at least one RLC entity corresponding tothe RB, MAC configuration information corresponding to each RLC entitycorresponding to the RB, logic channel configuration message, physicallayer configuration information, an identifier of a service, splitindication information and configuration information of a radio resourcecorresponding to the RB.

Preferably, the configuration information of the radio resourcecorresponding to the RB includes at least one of followings:

a physical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information.

In another preferable implementation manner of the embodiment of thepresent invention, the sending unit is configured to realize the sendingthe handover request acknowledge message to the source base station orthe core network node in a following manner:

sending the handover request acknowledge message to the source basestation to trigger the source base station to send a handover commandmessage to the user equipment, so as to enable the user equipment toestablish connections with the first target base station and the secondtarget base station; or

sending the handover request acknowledge message to the core networknode to trigger the core network node to send the handover requestacknowledge message to the source base station, thereby triggering thesource base station to send a handover command message to the userequipment, so as to enable the user equipment to establish connectionswith the first target base station and the second target base station.

Preferably, the receiving unit is further configured to receive a radioresource control RRC connection reconfiguration completion message sentby the user equipment, and control the first target base station toestablish a connection with the user equipment.

The sending unit is further configured to send, after the first targetbase station receives the RRC connection reconfiguration completionmessage sent by the user equipment, a handover indication message of theuser equipment to the second target base station, for indicating thatthe second target base station starts to use a resource configured tothe user equipment.

Preferably, the receiving unit is further configured to receive, afterthe first target base station sends the handover indication message ofthe user equipment to the second target base station, a handoverindication reply message of the user equipment sent by the second targetbase station, wherein the handover indication reply message of the userequipment comprises: third type of GTP tunnel endpoint informationcorresponding to an identifier of an RAB accepted by the second targetbase station, wherein the third type of GTP tunnel endpoint informationis used for requesting the core network node to switch a GTP tunnelendpoint.

Optionally, the sending unit is further configured to send, after thefirst target base station receives the RRC connection reconfigurationcompletion message sent by the user equipment, a path switch requestmessage to the core network node to request to hand over a servicecorresponding to the user equipment in the core network node to thefirst target base station and/or the second target base station.

The sending unit is configured to realize the sending the handoverrequest acknowledge message to the source base station or the corenetwork node in a following manner:

sending the handover request acknowledge message to the source basestation or the core network node to trigger the source base station tosend data and/or signaling of the user equipment in the source basestation to the first target base station and/or the second target basestation.

Optionally, the receiving unit is further configured to receive the dataand/or signaling of the user equipment sent by the source base station;and the sending unit is further configured to send corresponding part ofthe second target base station in the data and/or signaling of the userequipment to the second target base station.

Optionally, t the triggering the source base station to send the dataand/or signaling of the user equipment in the source base station to thefirst target base station and/or the second target base station,comprises:

triggering the source base station to send corresponding part of thefirst target base station in the data and/or signaling of the userequipment to the first target base station, and to send correspondingpart of the second target base station in the data and/or signaling ofthe user equipment to the second target base station.

Preferably, the data and/or signaling of the user equipment comprise(s)at least one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data ofthe service corresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN status transfer information and an end marker packet.

Optionally, the end marker packet is used for triggering the firsttarget base station and/or the second target base station to receivedata sent by a serving gateway in sequence.

In a preferable implementation manner of the embodiment of the presentinvention, the receiving unit is configured to realize the receiving thehandover request message sent by the source base station in a followingmanner: receiving the handover request message, which comes from thesource base station, forwarded by the core network node.

Embodiment 11

The embodiment of the present invention further provides a base station,and the base station may be taken as a first source base station toachieve embodiments 5 to 9 of the above-mentioned method.

FIG. 11 is a block diagram of a structure of a base station according tothe embodiment 11 of the present invention. As shown in FIG. 11, thebase station includes a receiving unit 20 and a sending unit 22, wherein

the sending unit is configured to send a handover request message to atarget base station, to make a request for a handover of a userequipment from the first source base station and a second source basestation to the target base station;

the receiving unit is configured to receive a handover requestacknowledge message sent by the target base station, wherein

the sending unit is further configured to send a handover commandmessage to the user equipment, to notify the user equipment to hand overfrom the first source base station and the second source base station tothe target base station.

Preferably, the sending unit is further configured to send, before thefirst source base station sends the handover request message to thetarget base station, a handover initiation request message to the secondsource base station, to make a request for a handover of the userequipment from the second source base station to the target basestation; and

the receiving unit is further configured to receive a handoverinitiation response message from the second source base station, andgenerating the handover request message according to the handoverinitiation response message.

Optionally, the sending unit is further configured to send, before thefirst source base station sends the handover request message to thetarget base station, a handover initiation request message to the secondsource base station through a local gateway; and the receiving unit isfurther configured to receive the handover request message from thelocal gateway, wherein the handover request message is generated by thelocal gateway according to a handover initiation response message fromthe second source base station.

In a preferable implementation manner of the embodiment of the presentinvention, the sending unit is further configured to send, after thefirst source base station receives the handover request acknowledgemessage sent by the target base station, a handover executionnotification message to the second source base station, for notifyingthe second source base station to start executing a handover operation.

Optionally, the receiving unit is further configured to receive ahandover execution notification response message sent by the secondsource base station, wherein the handover execution notificationresponse message comprises: SN status transfer information correspondingto at least one RAB served by the second source base station, and/or adata packet, in need of forwarding, corresponding to at least one RABserved by the second source base station.

Preferably, the receiving unit is further configured to receive thehandover request acknowledge message sent by the target base station fortriggering the first source base station and/or the second source basestation to send data and/or signaling of the user equipment to thetarget base station.

Optionally, the triggering the first source base station and/or thesecond source base station to send the data and/or signaling of the userequipment to the target base station comprises:

triggering the first source base station to send data and/or signalingof the user equipment in the first target base station and the secondtarget base station to the target base station; or

triggering the first source base station to send the data and/orsignaling of the user equipment in the first source base station to thetarget base station, and triggering the second source base station tosend data and/or signaling of the user equipment in the second sourcebase station to the target base station.

Preferably, the data and/or signaling of the user equipment comprise(s)at least one of followings: data of a service corresponding to the userequipment which has been sent without receiving a reply ACK, data of theservice corresponding to the user equipment with a NACK received, SDUdata, serial number SN status transfer information and an end markerpacket.

The receiving unit is further configured to receive, before the firstsource base station sends the end marker packet to the target basestation, the end marker packet sent by an S-GW.

Preferably, the sending unit is further configured to send the handoverrequest message to the target base station through a local gateway.

Embodiment 12

The embodiment of the present invention further provides a base station,and the base station may be taken as a source base station to achieveembodiments 1 to 4 of the above-mentioned method.

FIG. 12 is a block diagram of a structure of a base station according tothe embodiment 12 of the present invention. As shown in FIG. 12, thebase station includes a receiving unit 30 and a sending unit 32, wherein

a sending unit is configured to send a handover request message to afirst target base station;

a receiving unit is configured to receive a handover request acknowledgemessage sent by the first target base station, wherein the handoverrequest acknowledge message is used for notifying the source basestation to hand over the user equipment to at least one target cell ofthe first target base station and/or at least one target cell of thesecond target base station; and

the sending unit is further configured to send a handover commandmessage to the user equipment, to indicate the user equipment to handover to the first target base station and the second target basestation.

Preferably, the handover request message includes at least one offollowings: information of at least one target cell of the second targetbase station, measurement report information of the user equipment,context information of the user equipment and information of a serviceof the user equipment, wherein the information of the service includesRAB information of the service.

The information of the service may further include at least one offollowings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

Preferably, the GTP tunnel endpoint information is first type of GTPtunnel endpoint information or fourth type of GTP tunnel endpointinformation, wherein the first type of GTP tunnel endpoint informationis used for establishing a transmission bearer of an S1 interfacebetween a serving gateway S-GW and the first target base station and/orthe second target base station, and the fourth type of GTP tunnelendpoint information is used for establishing a transmission bearer forforwarding data between the first target base station and the secondtarget base station.

Optionally, the handover request acknowledge message comprises at leastone of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation between atleast one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; the second type of GTP tunnel endpoint informationis used for establishing a transmission bearer for data forwardingbetween the second target base station and the source base station.

Preferably, the first transparent container configuration includes atleast one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

Optionally, the configuration information of the RB includes at leastone of followings:

configuration information of a PDCP entity corresponding to the RB,configuration information of at least one RLC entity corresponding tothe RB, MAC configuration information corresponding to each RLC entitycorresponding to the RB, logic channel configuration message, physicallayer configuration information, an identifier of a service, splitindication information and configuration information of a radio resourcecorresponding to the RB.

Preferably, the configuration information of the radio resourcecorresponding to the RB includes at least one of followings:

a physical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information.

In a preferable implementation manner of the embodiment of the presentinvention, the receiving unit is configured to realize the receiving thehandover request acknowledge message sent by the first target basestation in a following manner: receiving the handover requestacknowledge message from the first target base station, which isforwarded by a core network element.

Preferably, the sending unit is configured to send, after the sourcebase station receives the handover request acknowledge message sent bythe first target base station, data and/or signaling of the userequipment to the first target base station and/or the second target basestation.

Optionally, the sending unit is configured to send, after the sourcebase station sends the handover command message to the user equipment,data and/or signaling of the user equipment to the first target basestation and/or the second target base station.

In another preferable implementation manner of the embodiment of thepresent invention, the sending unit is configured to realize the sendingthe data and/or signaling of the user equipment to the first target basestation and/or the second target base station in a following manner:

sending the data and/or signaling of the user equipment to the firsttarget base station, for enabling the first target base station to sendcorresponding part of the second target base station in the data and/orsignaling of the user equipment to the second target base station; or

sending corresponding part of the first target base station in the dataand/or signaling of the user equipment to the first target base station,and sending corresponding part of the second target base station in thedata and/or signaling of the user equipment to the second target basestation.

Preferably, the data and/or signaling of the user equipment comprise(s)at least one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data ofthe service corresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN status transfer information and an end marker packet.

Optionally, the end marker packet is used for triggering the firsttarget base station and/or the second target base station to receivedata sent by a serving gateway in sequence.

Preferably, the sending unit is configured to realize the sending thehandover request message to the first target base station in a followingmanner: sending the handover request message to the first target basestation through a core network node.

Embodiment 13

The embodiment of the present invention further provides a base station,and the base station may be taken as a target base station to achieveembodiments 5 to 9 of the above-mentioned method.

FIG. 13 is a block diagram of a structure of a base station according tothe embodiment 13 of the present invention. As shown in FIG. 13, thebase station includes a receiving unit 40 and a sending unit 42, wherein

the receiving unit is configured to receive a handover request messagesent by a first source base station, wherein the handover requestmessage is used for making a request for a handover of a user equipmentfrom the first source base station and a second source base station tothe target base station; and

the sending unit is configured to send a handover request acknowledgemessage to the first source base station, wherein the handover requestacknowledge message is used for indicating that the handover of the userequipment from the first source base station and the second source basestation to the target base station is accepted.

Preferably, the sending unit is further configured to receive, after thetarget base station sends the handover request acknowledge message tothe first source base station, data and/or signaling of the userequipment sent by the first source base station and/or the second sourcebase station.

Optionally, the receiving unit is configured to realize that the targetbase station receives the data and/or signaling of the user equipmentsent by the first source base station and/or the second source basestation in a following manner:

receiving the data and/or signaling of the user equipment sent by thefirst source base station, and/or receiving the data and/or signaling ofthe user equipment sent by the second source base station; or

receiving the data and/or signaling of the user equipment correspondingto the first source base station and/or the second source base station,sent by the first source base station.

Preferably, the data and/or signaling of the user equipment comprises atleast one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data of aservice corresponding to the user equipment with a NACK received, SDUdata, serial number SN status transfer information and an end markerpacket.

Optionally, the receiving unit is configured to realize the receivingthe handover request message sent by the first source base station in afollowing manner: receiving the handover request message, which comesfrom the first source base station, forwarded by a local gateway.

Preferably, the receiving unit is further configured to receive, afterthe target base station sends the handover request acknowledge messageto the first source base station, a radio resource control RRCconnection reconfiguration completion message sent by the userequipment, and control the target base station to establish connectionwith the user equipment.

Embodiment 14

The embodiment of the present invention further provides a base station,and the base station may be taken as a first target base station toachieve embodiments 1 to 4 of the above-mentioned method.

FIG. 14 is a block diagram of a structure of a base station according tothe embodiment 14 of the present invention. As shown in FIG. 14, thebase station includes a receiver 50 and a transmitter 52, wherein

the receiver is configured to receive a handover request message sent bya source base station or a core network node;

the transmitter is configured to send, according to the handover requestmessage, a first message to a second target base station to notify thesecond target base station that a handover of part or all of a serviceof a user equipment to the second target base station is to beperformed; and

the transmitter is further configured to send a handover requestacknowledge message to the source base station or the core network node,wherein the handover request acknowledge message is used for notifyingthe source base station or the core network node to hand over the userequipment to at least one target cell of the first target base stationand/or at least one target cell of the second target base station.

FIG. 15 is a block diagram of a specific structure of a base stationaccording to the embodiment 14 of the present invention. As shown inFIG. 15, the first target base station may further include: a processor54, wherein the processor is configured to determine, according to ameasurement report of the user equipment and/or radio access bear RABinformation of the user equipment in the handover request message, thatthe handover of the part or all of the service of the user equipment toa target cell of the second target base station; or determine, accordingto information of a target cell of the second target base station in thehandover request message, that the handover of the part or all of aservice of the user equipment to the second target base station; and thetransmitter is further configured to send the first message to thesecond target base station.

Preferably, the handover request message includes at least one offollowings: information of at least one target cell of the second targetbase station, measurement report information of the user equipment,context information of the user equipment and information of a serviceof the user equipment, wherein the information of the service includesRAB information of the service.

Optionally, the first message includes: information of at least oneservice of the user equipment, wherein the information of the serviceincludes RAB information of the service and/or configuration informationof a radio bear RB.

The information of the service further comprises at least one offollowings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

Preferably, the GTP tunnel endpoint information is first type of GTPtunnel endpoint information or fourth type of GTP tunnel endpointinformation, wherein the first type of GTP tunnel endpoint informationis used for establishing a transmission bearer of an S1 interfacebetween a serving gateway S-GW and the first target base station and/orthe second target base station, and the fourth type of GTP tunnelendpoint information is used for establishing a transmission bearer forforwarding data between the first target base station and the secondtarget base station.

Optionally, the configuration information of the RB comprises:

configuration information of a packet data convergence protocol PDCPlayer, a radio link control RLC layer, a medium access control MAC layerand a physical layer; or

configuration information of an RLC layer, an MAC layer and a physicallayer

Preferably, the receiver is further configured to receive a secondmessage sent by the second target base station after the first targetbase station sends the first message to the second target base station,wherein the second message is used for indicating information regardingwhether the handover of the part or all of the service of the userequipment to the second target base station is accepted by the secondtarget base station.

Optionally, the second message includes at least one of followings:

an identifier of the user equipment, first information and indicationinformation,

wherein the indication information includes at least one of followings:indication information of refusing the handover of the part or all ofthe service of the user equipment to the second target base station,indication information of accepting the handover of the part or all ofthe service of the user equipment to the second target base station, andindication information of modifying the first message;

the first information includes at least one of followings: an identifierof an RB accepted by the second target base station, configurationinformation of an RB accepted by the second target base station, anidentifier of an RAB corresponding to an RB accepted by the secondtarget base station, an identifier of an RB whose resource configurationis rejected by the second target base station, and an identifier of anRAB corresponding to an RB whose resource configuration is rejected bythe second target base station.

Optionally, the second message further includes at least one offollowings:

fourth type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe fourth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for forwarding data between the firsttarget base station and the second target base station;

second type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe second type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between thesecond target base station and the source base station; and

third type of GTP tunnel endpoint information corresponding to anidentifier of an RAB accepted by the second target base station, whereinthe third type of GTP tunnel endpoint information is used for requestinga core network node to convert a GTP tunnel endpoint.

Preferably, the handover request acknowledge message includes at leastone of followings:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation of at least oneRAB accepted by the first target base station and/or the second targetbase station and the first target base station and/or the second targetbase station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

Optionally, the first transparent container configuration includes atleast one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

Optionally, the configuration information of the RB includes at leastone of followings:

configuration information of a PDCP entity corresponding to the RB,configuration information of at least one RLC entity corresponding tothe RB, MAC configuration information corresponding to each RLC entitycorresponding to the RB, logic channel configuration message, physicallayer configuration information, an identifier of a service, splitindication information and configuration information of a radio resourcecorresponding to the RB.

Preferably, the configuration information of the radio resourcecorresponding to the RB includes at least one of followings:

a physical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information.

Optionally, the transmitter is configured to realize the sending thehandover request acknowledge message to the source base station or thecore network node in a following manner:

sending the handover request acknowledge message to the source basestation to trigger the source base station to send a handover commandmessage to the user equipment, so as to enable the user equipment toestablish connection with the first target base station and the secondtarget base station; or

sending the handover request acknowledge message to the core networknode to trigger the core network node to send the handover requestacknowledge message to the source base station, thereby triggering thesource base station to send the handover command message to the userequipment, so as to enable the user equipment to establish connectionswith the first target base station and the second target base station.

Preferably, the receiver is further configured to receive a radioresource control RRC connection reconfiguration completion message sentby the user equipment;

the first target base station further comprises: a processor, whereinthe processor is configured to establish a connection between the firsttarget base station and the user equipment after the first target basestation receives the radio resource control RRC connectionreconfiguration completion message sent by the user equipment.

Preferably, the transmitter is further configured to send, after thefirst target base station receives the RRC connection reconfigurationcompletion message sent by the user equipment, a handover indicationmessage of the user equipment to the second target base station, forindicating that the second target base station to starts use a resourceconfigured to the user equipment.

Optionally, the receiver is further configured to receive, after thefirst target base station sends the handover indication message of theuser equipment to the second target base station, a handover indicationreply message of the user equipment sent by the second target basestation, wherein the handover indication reply message of the userequipment comprises: third type of GTP tunnel endpoint informationcorresponding to an identifier of an RAB accepted by the second targetbase station, wherein the third type of GTP tunnel endpoint informationis used for requesting the core network node to switch a GTP tunnelendpoint.

Optionally, the transmitter is further configured to send, after thefirst target base station receives the RRC connection reconfigurationcompletion message sent by the user equipment, a path switch requestmessage to the core network node to request to hand over a servicecorresponding to the user equipment in the core network node to thefirst target base station and/or the second target base station.

Optionally, the transmitter is configured to realize the sending thehandover request acknowledge message to the source base station or thecore network node in a following manner:

sending the handover request acknowledge message to the source basestation or the core network node to trigger the source base station tosend data and/or signaling of the user equipment in the source basestation to the first target base station and/or the second target basestation.

Preferably, the receiver is further configured to receive the dataand/or signaling of the user equipment sent by the source base station;and

the transmitter is further configured to send corresponding part of thesecond target base station in the data and/or signaling of the userequipment to the second target base station.

Preferably, the triggering the source base station to send the dataand/or signaling of the user equipment in the source base station to thefirst target base station and/or the second target base station,comprises: triggering the source base station to send corresponding partof the first target base station in the data and/or signaling of theuser equipment to the first target base station, and to sendcorresponding part of the second target base station in the data and/orsignaling of the user equipment to the second target base station.

Preferably, the data and/or signaling of the user equipment comprise(s)at least one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data ofthe service corresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN state transfer information and an end marker packet.

Optionally, the end marker packet is used for triggering the firsttarget base station and/or the second target base station to receivedata sent by a serving gateway in sequence.

Preferably, the receiver is configured to realize the receiving thehandover request message sent by the source base station in a followingmanner: receiving the handover request message, which comes from thesource base station, forwarded by the core network node.

Embodiment 15

The embodiment of the present invention further provides a base station,and the base station may be taken as a first source base station toachieve embodiments 5 to 9 of the above-mentioned method.

FIG. 16 is a block diagram of a structure of a base station according tothe embodiment 15 of the present invention. As shown in FIG. 16, thebase station includes a receiver 60 and a transmitter 62, wherein

the transmitter is configured to send a handover request message to atarget base station, to make a request for a handover of a userequipment from the first source base station and a second source basestation to the target base station;

the receiver is configured to receive a handover request acknowledgemessage sent by the target base station; and

the transmitter is further configured to send a handover command messageto the user equipment, to notify the user equipment to hand over fromthe first source base station and the second source base station to thetarget base station.

Preferably, the transmitter is further configured to send, before thefirst source base station sends the handover request message to thetarget base station, a handover initiation request message to the secondsource base station, to make a request for a handover of the userequipment from the second source base station to the target basestation; and the receiver is further configured to receive a handoverinitiation response message from the second source base station, andgenerating the handover request message according to the handoverinitiation response message.

Optionally, the transmitter is further configured to send, before thefirst source base station sends the handover request message to thetarget base station, a handover initiation request message to the secondsource base station through a local gateway; and the receiver is furtherconfigured to receive the handover request message from the localgateway, wherein the handover request message is generated by the localgateway according to a handover initiation response message from thesecond source base station.

In a preferable implementation manner of the embodiment of the presentinvention, the transmitter is further configured to send, after thefirst source base station receives the handover request acknowledgemessage sent by the target base station, a handover executionnotification message to the second source base station, for notifyingthe second source base station to start executing a handover operation.

In another preferable implementation manner of the embodiment of thepresent invention, the receiver is further configured to receive ahandover execution notification response message sent by the secondsource base station, wherein the handover execution notificationresponse message comprises: SN status transfer information correspondingto at least one RAB served by the second source base station, and/or adata packet, in need of forwarding, corresponding to at least one RABserved by the second source base station.

Preferably, the receiver is further configured to receive the handoverrequest acknowledge message sent by the target base station fortriggering the first source base station and/or the second source basestation to send data and/or signaling of the user equipment to thetarget base station.

Preferably, the triggering the first source base station and/or thesecond source base station to send the data and/or signaling of the userequipment to the target base station comprises:

triggering the first source base station to send data and/or signalingof the user equipment in the first target base station and the secondtarget base station to the target base station; or

triggering the first source base station to send the data and/orsignaling of the user equipment in the first source base station to thetarget base station, and triggering the second source base station tosend the data and/or signaling of the user equipment in the secondsource base station to the target base station.

Optionally, the data and/or signaling of the user equipment comprises atleast one of followings: data of a service corresponding to the userequipment which has been sent without receiving a reply ACK, data of theservice corresponding to the user equipment with a NACK received, SDUdata, serial number SN status transfer information and an end markerpacket.

Preferably, the receiver is further configured to receive, before thefirst source base station sends the end marker packet to the target basestation, the end marker packet sent by an S-GW.

Optionally, the transmitter is further configured to send the handoverrequest message to the target base station through a local gateway.

Embodiment 16

The embodiment of the present invention further provides a base station,and the base station may be taken as a source base station to achieveembodiments 1 to 4 of the above-mentioned method.

FIG. 17 is a block diagram of a structure of a base station according tothe embodiment 16 of the present invention. As shown in FIG. 17, thebase station includes a receiver 70 and a transmitter 72, wherein

the transmitter is configured to send a handover request message to afirst target base station;

the receiver is configured to receive a handover request ackowledgemessage sent by the first target base station, wherein the handoverrequest ackowledge message is used for notifying the source base stationto hand over the user equipment to at least one target cell of the firsttarget base station and/or at least one target cell of a second targetbase station; and

the transmitter is further configured to send the handover commandmessage to the user equipment, to indicate the user equipment to handover to the first target base station and the second target basestation.

Preferably, the handover request message includes at least one offollowings: information of at least one target cell of the second targetbase station, measurement report information of the user equipment,context information of the user equipment and information of a serviceof the user equipment, wherein the information of the service includesRAB information of the service.

Optionally, the information of the service further comprises at leastone of followings:

configuration coordination information of a radio resource of an RB, anidentifier of an RB, an identifier of a radio access bear RAB, splitindication information and GTP tunnel endpoint information,

wherein the configuration coordination information of the radio resourceof the RB includes at least one of followings: a physical cellidentifier, a logic cell identifier, a virtual cell identifier,frequency information, carrier information, radio resource blockinformation, subcarrier information, sub-frame information, time domaininformation, code domain information and space domain information; thesplit indication information includes data split information based on anRB or data split information based on a packet.

Preferably, the GTP tunnel endpoint information is first type of GTPtunnel endpoint information or fourth type of GTP tunnel endpointinformation, wherein the first type of GTP tunnel endpoint informationis used for establishing a transmission bearer of an S1 interfacebetween a serving gateway S-GW and the first target base station and/orthe second target base station, and the fourth type of GTP tunnelendpoint information is used for establishing a transmission bearer forforwarding data between the first target base station and the secondtarget base station.

Optionally, the handover request reply message comprises at least one ofthe following items:

an identifier of the user equipment allocated at the source basestation, an identifier of the user equipment allocated at the firsttarget base station and/or the second target base station, a firsttransparent container configuration, an identifier of at least one RABrejected by the first target base station and/or the second target basestation, an identifier of at least one RAB accepted by the first targetbase station, fifth type of GTP tunnel endpoint informationcorresponding to an identifier of at least one RAB accepted by the firsttarget base station, an identifier of at least one RAB accepted by thesecond target base station, sixth type of GTP tunnel endpointinformation corresponding to an identifier of at least one RAB acceptedby the second target base station, second type of GTP tunnel endpointinformation corresponding to an identifier of an RAB accepted by thesecond target base station, and a corresponding relation between of atleast one RAB accepted by the first target base station and/or thesecond target base station and the first target base station and/or thesecond target base station,

wherein the fifth type of GTP tunnel endpoint information is used forestablishing a transmission bearer for data forwarding between the firsttarget base station and the source base station; the sixth type of GTPtunnel endpoint information is used for establishing a transmissionbearer for forwarding data between the first target base station and thesource base station; and the second type of GTP tunnel endpointinformation is used for establishing a transmission bearer for dataforwarding between the second target base station and the source basestation.

Optionally, the first transparent container configuration comprises atleast one of followings:

configuration information of at least one RB, and information of a cellof the first target base station and/or the second target base station,

wherein the RB is an RB corresponding to at least one RAB accepted bythe first target base station and/or the second target base station.

Preferably, the configuration information of the RB comprises at leastone of followings:

configuration information of a PDCP entity corresponding to the RB,configuration information of at least one RLC entity corresponding tothe RB, MAC configuration information corresponding to each RLC entitycorresponding to the RB, logic channel configuration message, physicallayer configuration information, an identifier of a service, splitindication information and configuration information of a radio resourcecorresponding to the RB.

Preferably, the configuration information of the radio resourcecorresponding to the RB includes at least one of followings:

a physical cell identifier, a logic cell identifier, a virtual cellidentifier, frequency information, carrier information, radio resourceblock information, subcarrier information, sub-frame information, timeslot information, time domain information, code domain information andspace domain information.

Optionally, the receiver is configured to realize the receiving thehandover request acknowledge message sent by the first target basestation in a following manner:

receiving the handover request acknowledge message from the first targetbase station, which is forwarded by a core network element.

In a preferable implementation manner of the embodiment of the presentinvention, the transmitter is configured to send, after the source basestation receives the handover request acknowledge message sent by thefirst target base station, data and/or signaling of the user equipmentto the first target base station and/or the second target base station.

In another preferable implementation manner of the embodiment of thepresent invention, the transmitter is configured to send, after thesource base station sends the handover command message to the userequipment, data and/or signaling of the user equipment to the firsttarget base station and/or the second target base station.

Preferably, the transmitter is configured to realize the sending thedata and/or signaling of the user equipment to the first target basestation and/or the second target base station in a following manner:

sending the data and/or signaling of the user equipment to the firsttarget base station, for enabling the first target base station to sendcorresponding part of the second target base station in the data and/orsignaling of the user equipment to the second target base station; or

sending corresponding part of the first target base station in the dataand/or signaling of the user equipment to the first target base station,and sending corresponding part of the second target base station in thedata and/or signaling of the user equipment to the second target basestation.

Preferably, the data and/or signaling of the user equipment comprise(s)at least one of followings: data of a service corresponding to the userequipment, which has been sent without receiving a reply ACK, data ofthe service corresponding to the user equipment, of which a response ofnon-acknowledgement NACK is received, data of service data unit SDU,serial number SN status transfer information and an end marker packet.

The end marker packet is used for triggering the first target basestation and/or the second target base station to receive data sent by aserving gateway in sequence.

Preferably, the transmitter is configured to realize the sending thehandover request message to the first target base station in a followingmanner: sending the handover request message to the first target basestation through a core network node.

Embodiment 17

The embodiment of the present invention further provides a base station,and the base station may be taken as a target base station to achieveembodiments 5 to 9 of the above-mentioned method.

FIG. 18 is a block diagram of a structure of a base station according tothe embodiment 17 of the present invention. As shown in FIG. 18, thebase station includes a receiver 80 and a transmitter 82, wherein

the receiver is configured to receive a handover request message sent bya first source base station, wherein the handover request message isused for making a request for a handover of a user equipment from thefirst source base station and a second source base station to the targetbase station; and

the transmitter is configured to send a handover request acknowledgemessage to the first source base station, wherein the handover requestacknowledge message is used for indicating that the handover of the userequipment from the first source base station and the second source basestation to the target base station is accepted.

Preferably, the transmitter is further configured to receive, after thetarget base station sends the handover request acknowledge message tothe first source base station, data and/or signaling of the userequipment sent by the first source base station and/or the second sourcebase station.

In a preferable implementation manner of the embodiment of the presentinvention, the receiver is configured to realize that the target basestation to receives the data and/or signaling of the user equipment sentby the first source base station and/or the second source base stationin a following manner: receiving the data and/or signaling of the userequipment sent by the first source base station, and/or receiving thedata and/or signaling of the user equipment sent by the second sourcebase station; or receiving the data and/or signaling of the userequipment corresponding to the first source base station and/or thesecond source base station, sent by the first source base station.

Preferably, the data and/or signaling of the user equipment comprise(s)at least one of followings: data of a service corresponding to the userequipment which has been sent without receiving a reply ACK, data of aservice corresponding to the user equipment with a NACK received, SDUdata, serial number SN status transfer information and an end markerpacket.

Optionally, the receiver is configured to realize the receiving thehandover request message sent by the first source base station in afollowing manner: receiving the handover request message, which comesfrom the first source base station, forwarded by a local gateway.

Preferably, the receiver is further configured to receive, after thetarget base station sends the handover request acknowledge message tothe first source base station, a radio resource control RRC connectionreconfiguration completion message sent by the user equipment, andcontrol the target base station to establish connection with the userequipment.

Through an embodiment of the present invention, after receiving thehandover request message, the first target base station notifies thesecond target base station that a handover of the user equipment thereonis to be performed, and sends the handover request acknowledge messageto the source base station, for notifying the source base station ofhanding over the user equipment to the first target base station and thesecond target base station, so that a handover can be realized whenthere exists a target cell. When there exist multiple source cells ofthe UE, one source cell therein (namely, the first source cell) sends arequest to the target base station to make a request for a handover theUE from multiple source cells to a target cell, thereby realizing thehandover of the UE from multiple source cells to one target cell.

The processor 54 in an above-mentioned embodiment of the presentinvention may be an integrated circuit chip having a signal processingcapacity, and may also be a hardware processor, such as a CPU and thelike. In an implementation process, each step of the above-mentionedmethod may be completed by an integrated logic circuit of hardware orinstructions in a software form in the processor. These instructions maybe cooperatively achieved and controlled by a processor therein. Forimplementing a method disclosed in an embodiment of the presentinvention, the above-mentioned processor may be a universal processor, adigital signal processor (DSP), an application-specific integratedcircuit (ASIC), a field programmable gate array (FPGA) or otherprogrammable logic devices, a discrete gate or a transistor logic deviceand a discrete hardware component, which realizes or implements eachmethod, step and logic block diagram disclosed in an embodiment of thepresent invention. The universal processor may be a microprocessor orthe processor may also be any common processor, decoder or the like. Astep of a method disclosed in an embodiment of the present invention maybe directly executed by a hardware processor, or executed by acombination of a hardware and a software module in a processor. Thesoftware module may be located in a mature storage media in the art,such as a random access memory, a flash memory, a read-only memory, aprogrammable read-only memory or an electrically erasable programmablememory, a register.

Through a description in an above-mentioned embodiment, those skilled inthe art to which the present invention pertains may clearly understandthat the present invention may be achieved by hardware, firmware or acombination thereof. When being achieved by a software, anabove-mentioned function may be stored in a computer readable medium ortransmitted as one or multiple instructions or codes on a computerreadable medium. The computer readable medium includes a computerstorage medium and a communication medium, wherein the communicationmedium includes any medium which is convenient to transmit a computerprogram from one place to another place. The storage medium may be anyavailable medium capable of being accessed by a computer, such as butnot limited to the computer readable medium may include an RAM, an ROM,an EEPROM, a CD-ROM, or other optical disk storage, magnetic diskstorage media or other magnetic storage devices, or any other mediacapable of being used for carrying or storing expected program codeswith instructions or in data structure forms and capable of beingaccessed by the computer. In addition, any connection may properlybecome a computer readable medium. For example, if software istransmitted from a website, a server or other remote sources by acoaxial cable, optical fiber and cable, a twisted pair, a digitalsubscriber line (DSL) or such wireless technologies as infrared, radioand microwave, then the coaxial cable, the optical fiber and cable, thetwisted pair, the DSL or such wireless technologies as infrared, radioand microwave are included in the photographic fixing of the affiliatedmedium. For example, the disk and disc adopted in the present inventioninclude a compact disc (CD), a laser disc, an optical disc, a digitaluniversal disc (DVD), a floppy disk and a Blu-ray disc, wherein the diskis generally used for magnetically copying data and the disc is used foroptically copying data by using laser. The above-mentioned combinationshould be included in the protection scope of the computer readablemedium.

To sum up, the foregoing description is merely a preferred embodiment ofthe technical solutions of the present invention, rather than limitingthe protection scope of the present invention. Any modification,equivalent substitution, improvement or the like, made within theessence and principle of the present invention, are still encompassed inthe protection scope of the present invention.

What is claimed is:
 1. A handover processing method, comprising:receiving, by a target base station, a handover request message sent bya first source base station, wherein the handover request message isused for making a request for a handover of a user equipment from thefirst source base station and a second source base station to the targetbase station; and sending, by the target base station, a handoverrequest acknowledge message to the first source base station, whereinthe handover request acknowledge message is used for indicating that thetarget base station accepts the handover of the user equipment from thefirst source base station and the second source base station to thetarget base station.
 2. The method of claim 1, wherein after thesending, by the target base station, the handover request acknowledgemessage to the first source base station, the method further comprises:receiving, by the target base station, data and/or signaling of the userequipment sent by the first source base station and/or the second sourcebase station.
 3. The method of claim 2, wherein the receiving, by thetarget base station, the data and/or signaling of the user equipmentsent by the first source base station and/or the second source basestation comprises: receiving, by the target base station, the dataand/or signaling of the user equipment corresponding to the first sourcebase station and/or the second source base station, sent by the firstsource base station.
 4. The method of claim 2, wherein the data and/orsignaling of the user equipment comprises at least one of followings:data of a service corresponding to the user equipment, which has beensent without receiving a reply ACK, data of a service corresponding tothe user equipment which a NACK received, Service Data Unit (SDU) data,serial number (SN) status transfer information and an end marker packet.5. The method of claim 1, wherein the receiving, by the target basestation, the handover request message sent by the first source basestation comprises: receiving, by the target base station, the handoverrequest message, which is sent from the first source base station, andis forwarded by a local gateway.
 6. The method of claim 1, wherein afterthe sending, by the target base station, the handover requestacknowledge message to the first source base station, the method furthercomprises: receiving, by the target base station, a radio resourcecontrol (RRC) connection reconfiguration completion message sent by theuser equipment, and establishing a connection with the user equipment.7. A network device, comprises: a receiver, configured to receive ahandover request message sent by a first source base station, whereinthe handover request message is used for making a request for a handoverof a user equipment from the first source base station and a secondsource base station to a target base station; and a transmitter,configured to send a handover request acknowledge message to the firstsource base station, wherein the handover request acknowledge message isused for indicating that the handover of the user equipment from thefirst source base station and the second source base station to thetarget base station is accepted.
 8. The network device of claim 7,wherein the receiver is further configured to receive, after the targetbase station sends the handover request acknowledge message to the firstsource base station, data and/or signaling of the user equipment sent bythe first source base station and/or the second source base station. 9.The network device of claim 8, wherein the receiver receives the dataand/or signaling of the user equipment sent by the first source basestation and/or the second source base station by implementing thefollowing: receiving the data and/or signaling of the user equipmentcorresponding to the first source base station and/or the second sourcebase station, sent by the first source base station.
 10. The networkdevice of claim 8, wherein the data and/or signaling of the userequipment comprise(s) at least one of followings: data of a servicecorresponding to the user equipment which has been sent withoutreceiving a reply ACK, data of a service corresponding to the userequipment with a NACK received, Service Data Unit (SDU) data, serialnumber SN status transfer information and an end marker packet.
 11. Thenetwork device of claim 7, wherein the receiver receives the handoverrequest message sent by the first source base station by implementingthe following: receiving the handover request message, which is sentfrom the first source base station, and is forwarded by a local gateway.12. The network device of claim 7, wherein the receiver is furtherconfigured to receive, after the target base station sends the handoverrequest acknowledge message to the first source base station, a radioresource control (RRC) connection reconfiguration completion messagesent by the user equipment, and control the target base station toestablish a connection with the user equipment.
 13. A communicationdevice, comprising: a processor; and a non-transitory memory, whereinthe memory stores an execution instruction, which when executed by theprocessor causes the communication device to perform operationsincluding: receiving an radio resource control (RRC) connectionreconfiguration message from a first source base station, when the userequipment is handing over from the first source base station and asecond source base station to a target base station, wherein the RRCconnection reconfiguration message comprises cell information of thetarget base station; and sending an RRC connection reconfigurationcompletion message.
 14. The communication device of claim 13, whereinthe RRC connection reconfiguration message further comprisesconfiguration information of a service and security information.
 15. Thecommunication device of claim 13, wherein the operations include:establishing a packet data convergence protocol (PDCP) layer entity, aradio link control (RLC) layer entity, a media access control (MAC)layer entity and a physical layer entity corresponding to a cellprotocol stack of the first target base station.
 16. The communicationdevice of claim 13, wherein the operations include: after a radio bearis configured successfully, forwarding a packet data convergenceprotocol (PDCP) service data unit (SDU) to a PDCP layer of a newlyestablished cell protocol stack of the first target base station and/ora newly established cell protocol stack of the second target basestation, wherein the PDCP SDU is an unordered PDCP SDU of a reorderingbuffer region in a PDCP entity in a user equipment protocol stackcorresponding to the source base station; and after the forwarding iscompleted, releasing each layer entity corresponding to a protocol stackof the first source base station in the user equipment, and each layerentity corresponding to a protocol stack of the second source basestation in the user equipment.